复制独立 HBase 0.2 部署
据我所知，当前的 HBase 稳定版本 0.2 不支持复制，尽管它已内置于 下一个版本。
您建议如何复制 HBase (0.2) 的独立（非分布式）部署？
我希望辅助实例用作工作备份，即只读。我可以承受具有“最终一致性”的异步备份，并且有少量损失（数据不重要）。
到目前为止，我唯一的想法是在写入主实例后手动异步更新辅助实例。
As far as I'm aware the current stable release of HBase, 0.2, does not support replication, although it is being built into the next version.
How would you recommend replicating a standalone (non-distributed) deployment of HBase (0.2) ?
I want the secondary instance to be used as a working backup i.e. read-only. I can afford asynchronous backups with "eventual consistency", and a small amount of loss (the data is non-critical).
So far my only thought was to manually update the secondary instance, asynchronously, after writing to the primary instance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
HBase 本身可以容忍节点故障/故障转移（假设您在 HDFS 上运行），因此实际上没有必要像使用 RDBMS 那样维护副本。
只使用 HDFS 复制有什么问题？
编辑：在这种情况下，您将从独立切换到分布式，并且只有 2 个复制因子为 2 的节点。
HBase natively tolerates node failure/failover (assuming that you are running on HDFS), so it's not really necessary to maintain a replica like you would with a RDBMS.
What's wrong with just using HDFS replication?
EDIT: In this case, you would switch from standalone to distributed, and just have 2 nodes with a replication factor of 2.