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

TopologyAwareConsistent hash not working as designed

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • None
    • 5.2.0.Beta4
    • Core
    • None

    Description

      The TACH does not appear to be functioning as designed. I specify two separate machines (3 nodes each), but the backups are not distributed on the machines.

      Here are TRACE logs (not of this system, unfortunately), but with the toString() of the CHF used. Here are the specific implementations:

      session-cluster (session, accountToSessionId, clientToSessionId): TACHF
      erm-cluster (serviceGroup, qamAllocation, eigAllocation): SyncTACHF

      https://dl.dropbox.com/u/50401510/10.30.12.159/server.log.gz
      https://dl.dropbox.com/u/50401510/10.30.12.160/server.log.gz
      https://dl.dropbox.com/u/50401510/10.30.12.163/server.log.gz

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-2566 TopologyAwareConsistentHashFactory rebalance doesn't redistribute data properly

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-2595 Consistent hash factory configuration is ignored

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: