The exception looks like this.
I am not able to understand the cause for this exception. I tried restarting the server but still it keeps occurring again and again.
问问题
63 次
1 回答
1
This is an ElasticSearch error and not something controlled by Moqui. I have seen this and based on my limited research it appears to happen when there are multiple ElasticSearch nodes running on the same network (in your case probably multiple Moqui nodes on the same network) and they seem to find the other nodes but not successfully sync up with them because they are not configured for it.
I haven't seen this cause any problems with anything else, so it seems annoying but safely ignored. There may be some ElasticSearch configuration that resolves this.
于 2014-09-20T07:17:23.957 回答