引用
From a technical standpoint, Luwak has some problems with the way in which files are chunked and manifest of those chunks is maintained.
Specifically, there is no good way of knowing when a given chunk is no longer in use, which creates a very thorny distributed garbage collection issue -- this is a fundamental design problem. In addition, the manifest of chunks does not properly handle situations where siblings of the manifest occur -- this is a significant implementation problem. These two issues, in particular, have led us to stop further development of Luwak and investigate other architectural approaches.
Above and beyond these technical issues, Luwak also doesn't solve a host of other problems that most people who want to store files in Riak encounter. We are in the process of building a complete solution for multi-tenancy file storage in Riak -- more info on that will be available next month.
Specifically, there is no good way of knowing when a given chunk is no longer in use, which creates a very thorny distributed garbage collection issue -- this is a fundamental design problem. In addition, the manifest of chunks does not properly handle situations where siblings of the manifest occur -- this is a significant implementation problem. These two issues, in particular, have led us to stop further development of Luwak and investigate other architectural approaches.
Above and beyond these technical issues, Luwak also doesn't solve a host of other problems that most people who want to store files in Riak encounter. We are in the process of building a complete solution for multi-tenancy file storage in Riak -- more info on that will be available next month.
一个替代模块在luwak终止后就在开发中，不过暂时不会开源。
新版的riak1.1依然可以使用luwak。
http://lists.basho.com/pipermail/riak-users_lists.basho.com/2012-February/007515.html
新模块和luwak没有任何关系， 不分享luwak的代码。
这个新的替代luwak的应用似乎已经实现了，在Riak CS上已经有 提供5GB的大数据支持：
但是，到目前为止（2011-5-24），即使是在 riak企业版中还没有看到对Large Object Support的支持。