GitHub PushEvent at 2014-12-15 16:27:49
Repository: elasticsearch
Actor: jaysonminard
Payload: {"shas":[["e47b753617302d0860d048fed0b6cd0ab2f6dcbb","f2d582bd23ffb37ba926272484fabf207d9e5aba@apache.org","[SEARCH] close active contexts on SearchService#close()\n\nWhen we close a node all pending / active search requests need to be\ncleared otherwise a node will wait up to 30 sec for shutdown sicne there\ncould be open scroll requests. This behavior was introduces in 1.5 such that\nversions <= 1.4.x are not affected.\n\nCloses #8940","Simon Willnauer",true],["9b18c44b676bbfbad94283deb6a3a66bd23e1108","cdedbaf433217656e9df940dd535438abed9f74c@writequit.org","Default _cat APIs to verbose\n\n`?v=false` can be used if the headers are not desired.\n\nResolves #8922\n\nFixes #8927","Lee Hinman",true],["d62bf5f67f102084fd66bf58744d5b30c26c4882","992531bec19101e9308e69893b3169c39fdfdd41@gmail.com","Discovery: concurrent node failures can cause unneeded cluster state publishing\n\nWhen a node fails (or closes), the master processes the network disconnect event and removes the node from the cluster state. If multiple nodes fail (or shut down) in rapid succession, we process the events and remove the nodes one by one. During this process, the intermediate cluster states may cause the node fault detection to signal the failure of nodes that are not yet removed from the cluster state. While this is fine, it currently causes unneeded reroutes and cluster state publishing, which can be cumbersome in big clusters.\n\nCloses #8804\nCloses #8933","Boaz Leskes",true],["fff483d612f8a97eb358c2d4ccad5b8e741e316f","d19c8a271c8b39f84e4be1b7dd44577f9c748eda@gmail.com","Docs: Adding REST ACL plugin\n\nCloses #8925","Simone Scarduzio",true],["23dbecf3e7e4848d40c203f86b856d433fe150d9","3323798efc8b1da40485ef75dd04e6c4d5451a87@gmail.com","Update percolate.asciidoc\n\nUpdating the `associated` spelling\n\nCloses #8907","Ayush",true],["ad747ba67f04cb4ddfd689cef0fc2398d3ff619f","a123eb83a22609df7b4913d05d4fdbad2ac69a4c@twitter.com","Docs: fix a typo in cluster stats documentation example\n\nCloses #8898","spapin",true],["a8fa650ee6a4c5ed25ff4b541d039d0cbd936c2c","cdedbaf433217656e9df940dd535438abed9f74c@writequit.org","[CORE] Remove IndexEngine\n\nIndexEngine was an abstraction where we had index-level engines (instead\nof shard-level) that could store meta information about the index. It\nwas never actually used by Elasticsearch, and only there for plugins.\n\nThis removes it, because it is a confusing abstraction and not needed,\nno plugins should be implementing their own IndexEngines.","Lee Hinman",true],["1247774ff1e91e762fe102d6e167f3da8c4a27ff","f2d582bd23ffb37ba926272484fabf207d9e5aba@apache.org","Remove Gateway abstraction\n\nWe only have a single gatweway since es 1.3. There is no need to keep all\nthese abstractsion and nested packages. We can fold most of it into simpler\nstructures.","Simon Willnauer",true],["3bba45289e33f71f0eb9f7146c44c9866362df7c","f2d582bd23ffb37ba926272484fabf207d9e5aba@apache.org","Remove unused code","Simon Willnauer",true],["01fc84dbb37758bea6a62a7f8471adb7208631f0","7658bca979a635f8885feb26fcbf4288a9fb3170@apache.org","Wire utf-8 encoding, so unicode filenames work\n\nSets -Dfile.encoding=UTF-8 by default.\n\nCloses #8847","Robert Muir",true],["8fbf45ef2be25cba8718ceefdd5dd4c0825c1a70","cdedbaf433217656e9df940dd535438abed9f74c@writequit.org","[TEST] Make parent breaker check less strict\n\nIn cases of heavy contention, it's possible for more than 2 threads\nto race to a circuit breaking exception.\n\nEssentially this means that if we have 3 threads all trying to add 3 and\nsimultaneously cause a circuit breaking exception (due to retry), when\nadjusting after circuit breaking we can \"rewind\" past what this test\nexpects the child breaker to be at.\n\nThis adds leeway into the check, where it's okay to be within\nNUM_THREADS from the parentLimit, because each thread should only add 1\nto the breaker at a time.","Lee Hinman",true]],"size":11,"ref":"refs/heads/master","head":"8fbf45ef2be25cba8718ceefdd5dd4c0825c1a70"}