Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-3998

quorum not established - java.net.SocketException: Connection reset seen in leader log

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.6.1
    • None
    • None
    • None
    • running zookeeper cluster (size 3) on kubernetes cluster 

       

    Description

      seeing an intermittent issue where the quorum is not reached, pods either 2nd or 3rd enters crashloopbackoff state .

      On inspecting the pod which keeps restarting, file with name as id, example "2" or ""3" is not created. 

      attaching the logs from all 3 nodes of ZK

      Attachments

        1. zk0.log
          95 kB
          priya Vijay
        2. zk1.log
          83 kB
          priya Vijay
        3. zk2.log
          15 kB
          priya Vijay

        Activity

          People

            Unassigned Unassigned
            priyavj priya Vijay
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: