Details
-
Bug
-
Resolution: Incomplete
-
Major
-
2.0-beta
-
Security Level: Public
Description
from prospect:
I just installed the 2.0 beta and with 2 nodes, CentOS 6.3, 64-bit and nothing talking to CB
top reports:
62 couchbas 20 0 281m 114m 2900 S 318.5 0.4 26:12.53 memcached
25681 couchbas 20 0 2079m 286m 6264 S 16.6 0.9 4:37.51 beam.smp
25660 couchbas 20 0 10880 580 428 S 0.0 0.0 0:00.00 epmd
25714 couchbas 20 0 103m 1188 1028 S 0.0 0.0 0:00.00 sh
25715 couchbas 20 0 4108 548 468 S 0.0 0.0 0:00.03 memsup
25716 couchbas 20 0 4104 404 328 S 0.0 0.0 0:00.00 cpu_sup
25718 couchbas 20 0 39028 1796 1448 S 0.0 0.0 0:00.02 ssl_esock
25720 couchbas 20 0 10844 508 408 S 0.0 0.0 0:00.19 inet_gethost
25721 couchbas 20 0 10844 424 308 S 0.0 0.0 0:00.10 inet_gethost
25763 couchbas 20 0 6320 572 472 S 0.0 0.0 0:00.32 sigar_port
25785 couchbas 20 0 411m 3004 1260 S 0.0 0.0 0:20.03 moxi
I'm at a loss to understand over 300% cpu usage when I only have the default bucket
and it's empty. The same is true on the other node in the cluster.
I restarted both servers in the cluster and brought them back up....same thing, ~300% cpu on both servers
with no clients attached. These nodes are the same exact hardware and are located in the same physical
chassis (Dell C6105)