Cassandra 快照和重启
作为 Linux (Ubuntu 9)、shell 和 cron 的 1 级新手,我在弄清楚这一点上遇到了一些困难。每天晚上,我都想拍摄 Cassandra 节点的快照并重新启动该过程。
为什么?因为我们的团队正在寻找内存泄漏,需要每 3 周左右重新启动一次进程。根本原因很难追查。与此同时,我想将这些 cron 作业落实到位以减少服务中断。
预先感谢任何已经了解其中一些内容的人!
Being a level 1 novice in Linux (Ubuntu 9), shell and cron, I've had some difficulty figuring this out. Each night, I'd like to take a snapshot of our Cassandra nodes and restart the process.
Why? Because our team is hunting down a memory leak that requires a process restart every 3 weeks or so. The root cause has been difficult to track down. In the meantime, I'd like to put these cron jobs in place to reduce service interruption.
Thanks in advance for anyone who has some of these already figured out!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
一般过程是:
运行nodetool快照时, JNA 的建立和运行非常重要。这包括:
如果这一切都是正确的,您应该启动时在日志中看到有关“mlockall”成功的消息。
另一件需要注意的事情是你的磁盘空间使用情况;随着压缩的发生和旧的 SSTable 被替换(但它们的快照仍然存在),这个数量将会增长。
The general procedure is:
When running nodetool snapshot, it is very important that you have JNA set up and working. This includes:
If this is all correct, you should see a message about "mlockall" succeeding in the logs on startup.
The other thing to keep an eye on is your disk space usage; this will grow as compactions occur and the old SSTables are replaced (but their snapshots remain).