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

PUSH based rehashing

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 5.0.0.CR8, 5.0.0.FINAL
    • 4.2.0.Final
    • Core

    Description

      Current rehash schemes are based on a PULL of state. Joiners (and new owners after a leave) pull state from their neighbours. This JIRA is to reimplement this as a PUSH based scheme, where all nodes detect new joiners (or leavers) and analyse their internal state and determine what needs to be pushed where.

      The scheme should be more robust, involving far fewer RPCs and coordination, and would work better for merge views detected when partitions heal.

      Based on Bela's prototype on https://github.com/belaban/infinispan/tree/rebalance-changes

      Attachments

        Issue Links

          blocks

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-1001 Should handle 3-way (or more) merges

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. ISPN-1106 Rehashing into a running cluster causes shared processing lock contention

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-1077 Multiple leaves are not handled correctly with DIST

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              dberinde@redhat.com Dan Berindei (Inactive)
              manik_jira Manik Surtani (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: