summaryrefslogtreecommitdiffstats
path: root/clustercontroller-core/pom.xml
diff options
context:
space:
mode:
authorTor Brede Vekterli <vekterli@yahoo-inc.com>2017-05-12 14:22:26 +0200
committerTor Brede Vekterli <vekterli@yahoo-inc.com>2017-05-12 14:38:36 +0200
commit1a17bb806379046a6ef513c3ef05e45d65028e19 (patch)
tree96bbdf3c26c9c375cd181cc1974bd55ff35e3b93 /clustercontroller-core/pom.xml
parentd25a365c86303637ae6db9a25d3149f87121ca83 (diff)
Always write new cluster state versions to ZooKeeper
Previously, the controller would not write the version to ZK unless the version was published to at least one node. This could lead to problems due to un-written version numbers being visible via the controller's REST APIs. External observers could see versions that were not present in ZK and that would not be stable across reelections. As a consequence, invariants for strictly increasing version numbers would be violated from the perspective of these external observers (in particular, our system test framework).
Diffstat (limited to 'clustercontroller-core/pom.xml')
-rw-r--r--clustercontroller-core/pom.xml5
1 files changed, 5 insertions, 0 deletions
diff --git a/clustercontroller-core/pom.xml b/clustercontroller-core/pom.xml
index 053f4efd2a7..42af701ac63 100644
--- a/clustercontroller-core/pom.xml
+++ b/clustercontroller-core/pom.xml
@@ -27,6 +27,11 @@
<scope>test</scope>
</dependency>
<dependency>
+ <groupId>org.hamcrest</groupId>
+ <artifactId>hamcrest-library</artifactId>
+ <scope>test</scope>
+ </dependency>
+ <dependency>
<groupId>org.codehaus.jettison</groupId>
<artifactId>jettison</artifactId>
</dependency>