AnsweredAssumed Answered

cldb is restarting frequently on M3 edition Cluster

Question asked by bgajjela on Jun 13, 2016
Latest reply on Jul 28, 2016 by Rachel Silver

Hi,

 

cldb is restarting frequently for a New M3 edition Cluster with below error.

 

 

 

2016-06-13 21:39:53,307 INFO ZKDataRetrieval [Thread-2-EventThread]: Process path: /services/cldb/master. Event state: SyncConnected. Event type: NodeDeleted

 

 

2016-06-13 21:39:53,308 INFO ZKDataRetrieval [Thread-2-EventThread]: Process path: /services_config/cldb/hostname. Event state: SyncConnected. Event type: NodeDataChanged

 

 

2016-06-13 21:39:53,311 ERROR ZKDataRetrieval [Thread-2-EventThread]: Can not get data from /services_config/cldb/hostname with error: KeeperErrorCode = NoNode for /services/cldb/hostname

 

 

2016-06-13 21:39:54,155 WARN Alarms [RPC-8]: Alarm raised: NODE_ALARM_SERVICE_CLDB_DOWN:hostname:NODE_ALARM; Cluster: SHAPESANDBOX; Node: hostname Message: Can not determine if service: cldb is running. Check logs at: /opt/mapr/logs/cldb.log

 

 

 

 

Few more errors

 

 

 

2016-06-13 22:03:38,931 INFO ZKDataRetrieval [Thread-2-EventThread]: Process path: /services/cldb. Event state: SyncConnected. Event type: NodeChildrenChanged

 

2016-06-13 22:03:38,934 INFO ZKDataRetrieval [Thread-2-EventThread]: Process path: /services/cldb. Event state: SyncConnected. Event type: NodeChildrenChanged

 

2016-06-13 22:03:38,940 INFO ZKDataRetrieval [Thread-2-EventThread]: Process path: /services_config/cldb/hostname. Event state: SyncConnected. Event type: NodeDataChanged

 

2016-06-13 22:03:38,943 INFO ZKDataRetrieval [Thread-2-EventThread]: Process path: /services_config/cldb/hostname. Event state: SyncConnected. Event type: NodeDataChanged

2016-06-13 22:03:39,800 WARN Alarms [RPC-4]: NODE_ALARM_SERVICE_CLDB_DOWN:hostname:NODE_ALARM cleared,

 

2016-06-13 22:03:54,825 INFO ZKDataRetrieval [Thread-2-EventThread]: Process path: /services/cldb/hostname. Event state: SyncConnected. Event type: NodeDataChanged

 

Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 7220; nested exception is:

        java.net.BindException: Address already in use

Outcomes