0

We are evaluating ChronicleMap and our application runs cluster mode with nodes ranging from 5 to 45. The plan is to have the ChronicleMap persisted in shared NFS folder so that all the nodes can read/write.

There are more likely chance that individual nodes could go down for various reasons in the middle of a read/write operation with this said. I have some questions

  1. If node-1 goes down during a write operation, can another healthy node-2 in the cluster still continue to read/write to the files?
  2. Lets say we implement some logic to detect a server crash and call the .recoverPersistedTo() on restart. Will this cause any issues while other healthy nodes in the cluster are reading/writing to the files? The reason I ask this question is that the document says

“You must ensure that no other process is accessing the Chronicle Map store when calling .recoverPersistedTo()”</p>

  1. I have read that using .recoverPersistedTo() in place is createPersistedTo() is not a good practice, but what are the downsides?
4

1 回答 1

0

首先，我们（Chronicle）不支持将 Chronicle Map 文件放在 NFS 上（因为我们使用内存映射并且 NFS 会导致问题）。此外，尝试在 NFS 上使用恢复将导致数据损坏，因为 NFS 上没有足够的文件锁定，并且恢复尝试锁定文件以防止多个进程同时恢复。一般来说，开源 Chronicle Map 应该被同一主机上的多个进程使用。

您的问题的解决方案是商业 Map Enterprise，它支持节点之间的地图复制，请联系 sales@chronicle.software 了解详情。

于 2020-09-24T11:41:40.267 回答