{"push_id":870969860,"size":1,"distinct_size":0,"ref":"refs/heads/master","head":"71cc55cacd9afac3756611f0866dbd5eee1ef079","before":"b30fdfebe30c9b6e37b9fbc3fec0ff74cd19f997","commits":[{"sha":"71cc55cacd9afac3756611f0866dbd5eee1ef079","author":{"email":"e9898c0da3098407dd316b9703e6c7444593ac82@gmail.com","name":"Arunachalam Thirupathi"},"message":"Update metadata version cluster, stores\n\nAt times metadata version on a cluster.xml and stores.xml drifts\nThe next metadata update instead of consolidating these versions\nupdates at few places and ignores at few other places.\n\nThis causes the client to not re-bootstrap correctly when the\ncluster.xml or stores.xml is changed.\n\nNow when a cluster.xml is changed, the version is synchronized\nacross the cluster to let the clients auto rebootstrap.\n\nThis fix merges the VectorClock on all the nodes to be updated\nso that the Stores version will be updated correctly.\n\nThe old methods which does not take nodes as parameters are removed\nand the public method exposes the nodes as parameters.","distinct":false,"url":"https://api.github.com/repos/arunthirupathi/voldemort/commits/71cc55cacd9afac3756611f0866dbd5eee1ef079"}]}