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

Rehashing into a running cluster causes shared processing lock contention

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 5.0.0.FINAL
    • 5.0.0.CR2
    • None
    • None

      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

        1. ISPN-1106.log
          90 kB
          Erik Salter

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

              Created:
              Updated:
              Resolved: