Uploaded image for project: 'controller'
  1. controller
  2. CONTROLLER-1632

IOException in initiateCaptureSnapshot

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • None
    • None
    • clustering
    • None
    • Operating System: All
      Platform: All

    • 8206

      odl: distribution-karaf-0.6.0-20170411.050836-4837.zip

      The test scenario follows the steps of DOMDataBroker testing: Leader Isolation: partition heals within transaction timeout
      1) start test-transaction producer, running at 1K tps, non-overlapping, from all nodes to a single shard
      2) Isolate leader
      3) Wait for followers to initiate election
      4) Un-isolate leader
      5) Wait for partition to heal - this was done within transaction timeout (30s)

      After the followers elected new leader, the node was rejoined (node unblocked via iptables).
      Then the test waited for all 3 nodes to be reported correctly. Few seconds after rejoin the node still reported IsolatedLeader raft state and then
      started to respond with http status 401 (unauthorized).
      This took

        1. log.html
          339 kB
        2. karaf_log_1.tar.gz
          65 kB
        3. karaf_log_2.tar.gz
          65 kB
        4. karaf_log_3.tar.gz
          64 kB

            Unassigned Unassigned
            pgubka@cisco.com Peter Gubka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: