gradle eclipse updates teh existing classpath and project and leaves teh classpath is a very inconsistent state. So removing these files and the users can generate them when required. Will fix the .gitignore to add these files so that they dont show up.
RestClient does not have POOL_SIZE_KEY anymore. From the source it is probably renamed to HTTP_POOL_SIZE. The previous constant value was poolsize and the new constant is http.poolsize. Upgrading the R2, Data, Pegasus libraries along with this change.
1. Created package voldemort.tools.admin 2. Developed structured admin command classes 3. Added structured help menus for each command 4. Implemented AdminTool utility classes 5. Added unit test for the new admin commands 6. Upgraded library jopt-simple to version 4.6
…ries and additional logging in RestHadoopFetcher
… to improve performance" This was part of performance benchmarking. It got wrong pushed to this branch. This reverts commit fe84793.
…oreClient instead of Thin client
.classpath - fixed error I introduced. *RebalanceTest.java - refactored to reduce cut&paste code - added comments and one TODO about attempting a proper fix wrt BindExceptions later. ServerTestUtils.java - renamed method back to startVoldemortServer - added 'throws BindException' test/unit/voldemort/scheduled/StreamingSlopPusherTest.java - added comment clarifying why this test is hard to harden against BindException issue
…tServer test/common/voldemort/ServerTestUtils.java - Renamed startVoldemortServer to startVoldemortServerInMannerThatMayResultInBindException (The name is intentionally long and annoying. There are some tests that must call this method bare, but that should be strongly discouraged!!!) - Added method header that encourages BindException to be caught and masked
…ently added tests: All of the following tests directly used the method ServerTestUtils.startVoldemortServer test/unit/voldemort/client/ClientRegistryTest.java test/unit/voldemort/client/AdminFetchTest.java test/unit/voldemort/client/EndToEndRebootstrapTest.java test/unit/voldemort/store/system/AsyncMetadataVersionManagerTest.java test/unit/voldemort/store/system/SystemStoreTest.java This method of starting Voldemort servers is susceptible to BindException errors. Unless something very fancy is being done, the method ServerTestUtils.startVoldemortCluster should be used to start a cluster within a test. test/unit/voldemort/client/ClientRegistryTest.java extended from TestCase. This is a "Junit3" idiom that we should not use in new tests. The Junit4 approach to tests relies solely on annotation.
…ed the Mlock related info messages to debug.
…p jars to 1.0.2
out all classes from batch commons
… list (VLinkedPagedList)
…to match LI stack..." This reverts commit acde9d9.
… LI stack...