Hey Folks,
We have a scenario here… we have 3 couchbase node under the same network, we have seen that one of the node(same everytime) goes down quite often.Checked the logs and we see following logs
1 - Haven’t heard from a higher priority node or a master, so I’m taking over.
2 - Enabled auto-failover with timeout 120 auto_failover 000 ns_xxxxxxxxxxxxxxxxxx
3 - Shutting down bucket “default” on ‘ns_xxxxxxxxxxxxxxx’ for server shutdown ns_memcached 000
4 - Node ‘ns_1@xxxxxxxxxxxxxxx’ saw that node ‘ns_1@xxxxxxxxxxxxxxx’ went down Details: [{nodedown_reason, connection_closed}] …ns_node_disco_005
5 - Service ‘ns_server’ exited with status 1. Restarting. Messages: [os_mon] win32 supervisor port (win32sysinfo): Error writing to pipe {“Kernel pid terminated”,application_controller,"{application_terminated,os_mon,shutdown}"}
Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller) ({application_terminated,os_mon,shutdown})
After few seconds log says that it is able to contact the node…
6 - Couchbase Server has started on web port 8091 on node ‘ns_1@XXXXXXXXX’. Version: “4.5.0-2601-enterprise”.
7 - Node ‘ns_1@xxxxxxxxxx’ saw that node ‘ns_1@xxxxxxxxxx’ came up. Tags:
8 - Default,core and mobile buckets were loaded after node was up.
Any suggestions is appreciated…
Regards,
Shan