Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-1106

Rehashing into a running cluster causes shared processing lock contention

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • 5.0.0.CR2
    • 5.0.0.FINAL
    • None
    • None

    Description

      On our initial test of 5.0.0.CR2, we wanted to test the cluster's rehashing behavior/performance and if all locks were cleaned up.

      The test was to start two nodes, then add a third node, all the while issuing commands to it.

      Upon adding a third node, the cluster becomes inoperable. The stack traces is in the following location:

      http://dl.dropbox.com/u/10929737/5.0.0.CR2/server_node1.log,
      http://dl.dropbox.com/u/10929737/5.0.0.CR2/server_node2.log,
      http://dl.dropbox.com/u/10929737/5.0.0.CR2/server_node3.log

      Attachments

        1. ISPN-1106.log
          90 kB
          Erik Salter

        Issue Links

          Activity

            People

              dberinde@redhat.com Dan Berindei
              esalter@synamedia.com Erik Salter (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: