Random server shut down

Couchbase Server
1

Hi guys we have been triggering manual compaction since a couple of days ago on our
production servers, but recently for some unknown reason our second server on the
cluster went down, the logs were the following

Node ‘ns_1@###.##.##.###’ saw that node ‘ns_1@###.##.##.###’ went down. Details: [{nodedown_reason,
net_tick_timeout}] ns_node_disco 005 ns_1@###.##.##.### 3:46:22 PM Thu May 25, 2017
Node ‘ns_1@###.##.##.###’ saw that node ‘ns_1@###.##.##.###’ went down. Details: [{nodedown_reason,
net_tick_timeout}] ns_node_disco 005 ns_1@###.##.##.### 3:46:15 PM Thu May 25, 2017
Shutting down bucket “server_x_shadow” on ‘ns_1@###.##.##.###’ for server shutdown ns_memcached 000 ns_1@###.##.##.### 3:14:04 PM Thu May 25, 2017
Shutting down bucket “server_x_database” on ‘ns_1@###.##.##.###’ for server shutdown ns_memcached 000 ns_1@###.##.##.### 3:14:04 PM Thu May 25, 201

For some reason the both databases were shutdown on that server because
something triggered a shutdown, i don’t even know what.

Why could a server possibly shutdown itself?

2

We recently experienced the same issue twice in two months.

Shutting down bucket “BUCKET1” on ‘ns_1@XXX.XX.XX.XXX’ for server shutdown ns_memcached000 ns_1@XXX.XX.XX.XXX 17:22:30 - Wed Jun 21, 2017
Shutting down bucket “BUCKET2” on ‘ns_1@XXX.XX.XX.XXX’ for server shutdown ns_memcached000 ns_1@XXX.XX.XX.XXX 17:22:30 - Wed Jun 21, 2017
Shutting down bucket “BUCKET3” on ‘ns_1@XXX.XX.XX.XXX’ for server shutdown ns_memcached000 ns_1@XXX.XX.XX.XXX 17:22:30 - Wed Jun 21, 2017