Now this is making me really annoying…
The server is keep going down when rebalancing the cluster.
I had to reboot my AWS instance and the cluster is re-indexing the bucket.
And I am doing this for about 5 times straight.
Please, anyone help me.
Hardware spec:
EC2 m3.xlarge
vCPU: 4
Ram: 15043 MB
Disk: 300GB
Cluster configuration:
Couchbase Server CE 3.0.1
3 nodes
1 bucket
Per Node RAM Quota: 10000 MB
Cluster RAM Quota: Per Server RAM Quota: 10000 MB
9 Design view
Numbers:
Item Count: 21,000,000
Indexing time: 5 hrs
Logs:
Node ‘ns_1@172.31.4.173’ saw that node ‘ns_1@172.31.9.105’ went down. Details: [{nodedown_reason,
net_tick_timeout}] ns_node_disco005 ns_1@172.31.4.173 04:07:04 - Thu Jun 11, 2015
Rebalance exited with reason {{nodedown,‘ns_1@172.31.9.105’},
{gen_server,call,
[{‘janitor_agent-userhabit’,
‘ns_1@172.31.9.105’},
{if_rebalance,<0.3289.14>,
{uninhibit_view_compaction, #Ref17012.0.122.9318>}},
infinity]}}
ns_orchestrator002 ns_1@172.31.13.128 04:07:04 - Thu Jun 11, 2015
<0.7072.15> exited with {{nodedown,‘ns_1@172.31.9.105’},
{gen_server,call,
[{‘janitor_agent-userhabit’,‘ns_1@172.31.9.105’},
{if_rebalance,<0.3289.14>,
{uninhibit_view_compaction, #Ref<17012.0.122.9318>}},
infinity]}}
Node ‘ns_1@172.31.13.128’ saw that node ‘ns_1@172.31.9.105’ went down. Details: [{nodedown_reason,
net_tick_timeout}]
Some documents tell me to turn off auto-compaction while rebalancing, so I tried but it didn’t help. A server still going down.
While rebalancing, RAM usage goes over 95%. Is this even normal?
I couldn’t sleep because of this for the last 2 days.
Please someone help me…