Hi Yinyong,
We use LogCabin at Scale Computing in production. We have thousands of instances running in 1, 3 and 5 node configurations. We first started using it when Diego was finishing up his thesis. He worked with us on some bugs we found running it through our test harness. It's been pretty much bug free since the last commits were merged. I have one outstanding bug fix commit where a client can crash when initializing the RNG if you are at your fd limit.
Overall the experience has been great. A lot of it is due to the raft protocol itself, linearizability makes several things easier when you are running code on a cluster, and having the client handle failures for you seamlessly is far better than what you have to do in other instances. The code itself is clean, unit tested and fairly easy to understand. The thesis and code are extremely well matched, it's easy to find the reasoning for code in the thesis or implementation of an idea in the code.
Diego has no future plans for LogCabin and has pretty much gone unresponsive to any PRs or emails related to LogCabin. I am not sure what that means for the future of the project. We will continue to use it at Scale and will fix any bugs that affect us. What I've done in the past is push those to github and open a PR to the main project.
There is a logcabin-dev mailing list. Not much traffic but people that have signed up there do have some interest in the project going forward. If you do decide to use it, need tips or want to coordinate on where to put new patches, that might be a good place for it.
Nate