commit | 37529e39f6624d58bef5c4ec5110746cc59db243 | [log] [tgz] |
---|---|---|
author | jiajunwang <1803880+jiajunwang@users.noreply.github.com> | Tue Jul 30 14:41:32 2019 -0700 |
committer | Jiajun Wang <jjwang@jjwang-ld2.linkedin.biz> | Thu Aug 01 12:31:44 2019 -0700 |
tree | 3803a2ffa3e4ea6ec90c761f5cf83198f0161695 | |
parent | 4c34be0639931a29074509b0e1cf9cee2495ec72 [diff] |
Fix the race condition while Helix refresh cluster status cache. (#363) * Fix the race condition while Helix refresh cluster status cache. This change fix issue #331. The design is ensuring one read only to avoid locking during the change notification. However, a later update introduced addition read. The result is that two reads may have different results because notification is lock free. This leads the cache to be in an inconsistent state. The impact is that the expected rebalance might not happen.
Helix is part of the Apache Software Foundation.
Project page: http://helix.apache.org/
Mailing list: http://helix.apache.org/mail-lists.html
mvn clean install package -DskipTests
Helix is a generic cluster management framework used for automatic management of partitioned, replicated and distributed resources hosted on a cluster of nodes. Helix provides the following features: