…ack from fetch function instead of null. This improves Azkaban visibility.
… block. This is meant to get around the intermittent Hadoop failures.
the keys are actually in the server
the streamingclient consumer may implement a time based flushing through a scheduled executor service or a timer thread(like in YASP) this helps achieveing a lock step access
Added windows batch files. See comment in header of each file that these BAT files are not tested with each Voldemort release. We hope this helps the community, but cannot commit to testing each release on windows.
Updated copyright info to make clear that these files are not maintained by LinkedIn
Added file option to generate_cluster_xml
verifyschema() now takes the schema of the subfiled rather than entire record if this property is enforced
periodically exposed the commit method
.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.
… GC or other pause occurs at inopportune point during test.
…r to long unit test. Cleaned up comments in ClientRequestExecutorPool to make intended semantics clearer.
- renamed base keyedresourcepool test to avoid pattern that ant/junit uses to try and run tests. - tweaked stress tests parameters once more to make it easier to run locally.