在Riak中存储二进制数据的缺点? [英] Downsides of storing binary data in Riak?

查看:434
本文介绍了在Riak中存储二进制数据的缺点?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在Riak中存储二进制数据有什么问题?

What are the problems, if any, of storing binary data in Riak?

它是否会影响集群的可维护性和性能?

Does it effect the maintainability and performance of the clustering?

对于这个而不是分布式文件系统,使用Riak之间的性能差异是什么?

What would the performance differences be between using Riak for this rather than a distributed file system?

推荐答案

添加到@ Oscar-Godson的优秀答案,你可能会遇到大于50MB的值的问题。 Bitcask最适合于高达几KB的值。如果您要存储较大的值,则可以考虑使用其他存储后端,例如 innostore

Adding to @Oscar-Godson's excellent answer, you're likely to experience problems with values much larger than 50MBs. Bitcask is best suited for values that are up to a few KBs. If you're storing large values, you may want to consider alternative storage backends, such as innostore.

我没有存储二进制值的经验,但我们在生产中有一个中型集群(5个节点,大约100M值,10个TB),我们看到与插入和检索大小为100 KB的值相关的常见错误。在这种情况下的性能是不一致的 - 有时它的工作,其他它不 - 所以如果你要测试,大规模测试。

I don't have experience with storing binary values, but we've a medium-sized cluster in production (5 nodes, on the order of 100M values, 10's of TBs) and we're seeing frequent errors related to inserting and retrieving values that are 100's of KBs in size. Performance in this case is inconsistent - some times it works, others it doesn't - so if you're going to test, test at scale.

我们也在运行map-reduce查询时看到大值的问题 - 它们只是超时。但是,这可能与二进制值不太相关...(正如@ Matt-Ranney提到的)。

We're also seeing problems with large values when running map-reduce queries - they simply time out. However that may be less relevant to binary values... (as @Matt-Ranney mentioned).

另见@ Stephen-C的回答在这里

Also see @Stephen-C's answer here

这篇关于在Riak中存储二进制数据的缺点?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆