{"push_id":982228503,"size":1,"distinct_size":1,"ref":"refs/heads/develop","head":"e89b7e66e81a2d3aebafe647223a479fdd75e4c3","before":"c358cc1664ab7c4582b348869a167f119580115f","commits":[{"sha":"e89b7e66e81a2d3aebafe647223a479fdd75e4c3","author":{"email":"917229b7dd48e6ac78c60f5295cb546d253427fb@vmware.com","name":"Alain Roy"},"message":"Allow CloudStoreConstraintChecker to use broadcast queries\n\nPreviously the CloudStoreConstraintChecker would only query a single\nCloudStore host. That worked fine when we had no more than three\nCloudStore nodes because CloudStore is configured to replicate all\ndata to three nodes. However, when there are four or more CloudStore\nnodes, data is not symmetrically broadcaast to all nodes so we have to\nuse broadcast queries.\n\nThis change adds the use of broadcast queries and extends the tests to\nuse five CloudStore nodes. Broadcast queries return a different\nresponse type and do not collate results in the same way, so we handle\nthem differently.\n\nNote that the code only uses broadcast queries when required. This is\na performance optimization but does not affect correctness.\n\nChange-Id: Iae6db150979a5019c302ef97990c3986c0c6af2d","distinct":true,"url":"https://api.github.com/repos/vmware/photon-controller/commits/e89b7e66e81a2d3aebafe647223a479fdd75e4c3"}]}