[FLUME-436] Reduce the severity of being unable to connect to a master

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.3
• Component/s: Easy, Node
• Assignee: Jonathan Hsieh
• Reporter: Jonathan Hsieh
• Created: 28/Dec/10 19:54
• Updated: 05/Jan/11 21:23
• Resolved: 05/Jan/11 21:23

Description

This is a scary message that could probably go down to WARN mode without the stack dump.

---

10/12/27 18:16:20 ERROR agent.MultiMasterRPC: Unable to find a master server
java.io.IOException: Could not connect to any master nodes (tried 1: [xxxx.com:35872])
at com.cloudera.flume.agent.MultiMasterRPC.findServer(MultiMasterRPC.java:129)
at com.cloudera.flume.agent.MultiMasterRPC$RPCRetryable.doTry(MultiMasterRPC.java:196)
at com.cloudera.util.RetryHarness.attempt(RetryHarness.java:64)
at com.cloudera.flume.agent.MultiMasterRPC.getLogicalNodes(MultiMasterRPC.java:254)
at com.cloudera.flume.agent.LivenessManager.checkLogicalNodes(LivenessManager.java:98)
at com.cloudera.flume.agent.LivenessManager.heartbeatChecks(LivenessManager.java:154)
at com.cloudera.flume.agent.LivenessManager$HeartbeatThread.run(LivenessManager.java:181)