| commit | f2cf203fb2901769c2c6035af11a4310af8ac19a | [log] [tgz] |
|---|---|---|
| author | Joseph Koshakow <jkosh44@users.noreply.github.com> | Fri Mar 06 21:46:00 2020 -0500 |
| committer | GitHub <noreply@github.com> | Fri Mar 06 21:46:00 2020 -0500 |
| tree | 0dca0352db46ec59153fec786e6c1a931c638a3e | |
| parent | 4ecd4560e76a6ac44f7e80f75f5e42dcad86dddf [diff] |
Use LeaderLatch to determine if oracle exists (#1088) * Use LeaderLatch to determine if oracle exists The old implementation of oracleExists checks to see if there are more than 1 ZNodes under the ZookeeperPath.ORACLE_SERVER path. This relies on the LeaderLatch implementation and uses a path given to a Curator recipe, which is advised against by the Curator docs. See https://cwiki.apache.org/confluence/display/CURATOR/TN7. The new implementation utilizes LeaderLatch to count the number of participants to see if there's more than 0.
Apache Fluo is a distributed processing system that lets users make incremental updates to large data sets. With Apache Fluo, users can set up workflows that execute cross node transactions when data changes. These workflows enable users to continuously join new data into large existing data sets without reprocessing all data. Apache Fluo is built on Apache Accumulo. Check out the Fluo project website for news and general information.