Uploaded image for project: 'Flume (READ-ONLY)'
  1. Flume (READ-ONLY)
  2. FLUME-436

Reduce the severity of being unable to connect to a master

          Details

          • Type: Improvement
          • Status: Resolved
          • Priority: Major
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: v0.9.3
          • Component/s: Easy, Node
          • Labels:
            None

            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)

              Attachments

                Activity

                  People

                  • Assignee:
                    jon Jonathan Hsieh
                    Reporter:
                    jon Jonathan Hsieh
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: