Bug 1118650
Summary: | 13.3. Hot Rod Hash Functions, consistent hash function | ||
---|---|---|---|
Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Vitalii Chepeliuk <vchepeli> |
Component: | Documentation | Assignee: | Misha H. Ali <mhusnain> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.0 | CC: | jdg-bugs, mhusnain, vchepeli |
Target Milestone: | GA | ||
Target Release: | 6.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
Build Name: 12532, Administration and Configuration Guide-6.3
Build Date: 07-07-2014 11:21:19
Topic ID: 6721-635853 [Latest]
|
|
Last Closed: | 2014-07-21 02:14:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Vitalii Chepeliuk
2014-07-11 08:37:37 UTC
Misha can you change text about hashing to this one The hashing algorithm in JBoss Data Grid is based on consistent hashing, and even though our implementation has diverged a bit, we still use the term consistent hash. Unlike in consistent hashing, we split the key space into fixed segments. The number of segments is configurable (numSegments), and it cannot be changed without restarting the cluster. The mapping of keys to segments is also fixed — a key should map to the same segment, regardless of how the topology of the cluster changes. Each hash segment is mapped to a list of nodes called owners. The order matters, because the first owner, also known as the primary owner, has a special role in many cache operations (e.g. locking). The other owners are called backup owners. There is no hard rule on how the segments are mapped to owners, although the hashing algorithms generally try to balance the number of segments allocated to each node and at the same time minimize the number of segments that have to move after a node joins or leaves the cluster. Sure, Vitalii. Updating now. Now available on access.redhat.com under the JBoss Data Grid 6.3 documentation label. |