Switch branches/tags
vector-clock-fixes v1.4.0 release-1.10.26-cutoff release-1.10.25-cutoff release-1.10.24-cutoff release-1.10.23-cutoff release-1.10.22-cutoff release-1.10.21-cutoff release-1.10.20-cutoff release- release-1.10.19-cutoff release-1.10.18-cutoff release-1.10.17-cutoff release-1.10.16-cutoff release-1.10.15-cutoff release-1.10.14-cutoff release-1.10.13-cutoff release-1.10.12-cutoff release-1.10.11-cutoff release-1.10.10-cutoff release-1.10.9-cutoff release-1.10.8-cutoff release-1.10.7-cutoff release-1.10.6-cutoff release-1.10.5-cutoff release-1.10.4-cutoff release-1.10.3-cutoff release-1.10.2-cutoff release-1.10.1-cutoff release-1.10.0-cutoff release-1.9.22-cutoff release-1.9.21-cutoff release-1.9.20-cutoff release-1.9.19-cutoff release-1.9.18-cutoff release-1.9.17-cutoff release-1.9.16-cutoff release-1.9.15-cutoff release-1.9.14-cutoff release-1.9.13-cutoff release-1.9.12-cutoff release-1.9.11-cutoff release-1.9.10-cutoff release-1.9.9-cutoff release-1.9.8-cutoff release-1.9.7-cutoff release-1.9.6-cutoff release-1.9.5-cutoff release-1.9.4-cutoff release-1.9.3-cutoff release-1.9.2-cutoff release-1.9.1-cutoff release-1.9.0-cutoff release-1.8.16-cutoff release-1.8.15-cutoff release-1.8.14-cutoff release-1.8.13-cutoff release-1.8.12-cutoff release-1.8.11-cutoff release-1.8.10-cutoff release-1.8.9-cutoff release-1.8.8-cutoff release-1.8.5-cutoff release-1.8.4-cutoff release-1.8.3-cutoff release-1.8.1-cutoff release-1.7.3-cutoff release-1.7.2-cutoff release-1.7.1-cutoff release-1.7.0-cutoff release-1.6.8-cutoff release-1.6.6-cutoff release-1.6.4 release-1.6.4-cutoff release-1.6.3-cutoff release-1.6.2-cutoff release-1.6.1-cutoff release-1.6.0-cutoff release-1.5.9-cutoff release-1.5.8-cutoff release-1.5.7-cutoff release-1.5.4-cutoff release-1.5.2-cutoff release-1.5.1-cutoff release-1.3.0-cutoff before-replicatype-was-removed before-donorbased-was-removed
Nothing to show
Commits on Oct 31, 2012
  1. Prepared release 1.1.2

    jayjwylie committed Oct 31, 2012
Commits on Oct 30, 2012
Commits on Oct 29, 2012
  1. Fixes for connection leak and ZenStoreClient config

    jayjwylie committed Oct 29, 2012
    - Applied fix for socketChannel leak in ClientRequestExecutorFactory.create()
    - Added comments to document other code paths at risk of leaking socketDestinations
    - changed ClientConfig default from ZenStoreClient to DefaultStoreClient
    - updated release notes
Commits on Oct 19, 2012
  1. Added parameters to control retention job

    vinothchandar committed Oct 1, 2012
    1. day of the week the retention job starts
    2. if the retention job starts at the same hour each day
  2. Upgrading to JE 4.1.17

    vinothchandar committed Aug 31, 2012
  3. Code review changes

    vinothchandar committed Aug 2, 2012
Commits on Oct 18, 2012
Commits on Oct 17, 2012
  1. Tweaked release notes

    jayjwylie committed Oct 17, 2012
  2. Hardened junit long test Other test hardening.

    jayjwylie committed Oct 17, 2012
    - bumped all maxmemory settings to 2048m
    - Placed a 90 minute timeout on the long test at ant level.
    - null out some objects in the hopes of reducing the overall memory footprint of these tests. We are truly abusing junit with a long-running, multi-threaded test, that has 10 sub tests and 4 distinct parameter settings.
    - start of tests is not clear in junit log output. Added to start of tests to make grepping through the log when tests have failed badly and/or are running in an infitie loop easier.
    - Bumped each test timeout up to 10 minutes. Again, note abuse of junit: tests should not be defined at the abstract class level. This makes it hard to set appropriate limits (such as timeout) for each specific test. Long tests should have a different timeout than short tests...
Commits on Oct 16, 2012
  1. Added two tools for repeatedly running junit tests. Either specific t…

    jayjwylie committed Oct 15, 2012
    …ests, or all of junit. The benefit of these scripts is that the results from each run are archived toa temp directory. This allows you to stress test big changes, find intermittent failures, and so on.
  2. Additional hardening of tests to reduce the number of intermittent

    jayjwylie committed Oct 12, 2012
    BindException errors due to a TOCTOU issue with getLocalCluster.
    - switched to startVoldemortCluster
    - hand-coded test-specific startParallelVoldemortCluster. Not pretty. Not pretty at all. But, should retry in the face of such exceptions.
    Switched TODO to comment about possible susceptability to BindExceptions:
    - test/unit/voldemort/client/rebalance/
    - test/unit/voldemort/scheduled/
  3. Hardening test utils and tests to reduce the number of intermittent

    jayjwylie committed Oct 12, 2012
    BindException errors due to a TOCTOU issue with getLocalCluster.
    The main improvement is the addition of
    ServerTestUtils.startVoldemortCluster that wraps getLocalCluster and a
    bunch of startVoldemortServer calls in a retry loop based on wether a
    BindException occurs. This is suitable to ~75% of our test cases that
    use getLocalCluster.
    - Added startVoldemortCluster
    - Tests for ServerTestUtils to reproduce intermittent failures
    - TODO note about method that plays a role in another intermittent test failure invovling cluster.xml
    Switched test to use startVoldemortCluster
    Junit3 -> Junit 4
    Annotated with a TODO about the test still needing to be hardened
    against TOCTOU issue with getLocalCluster:
  4. Adding a specific mini test that exercises ServerTestUtils.startVolde…

    jayjwylie committed Sep 12, 2012
    …mortServer. This ~15 line program that simply starts some Voldemort servers using test utils can tickle two different intermittent failures:
    (1) ObsoleteVersionException when loading cluster.xml
    Testcase: startMultipleVoldemortServers took 0.385 sec
    	Caused an ERROR
    A successor version version()  to this version() exists for key cluster.xml
    voldemort.versioning.ObsoleteVersionException: A successor version version()  to this version() exists for key cluster.xml
    (2) A bind issue characterized as follows:
    Testcase: startMultipleVoldemortServers took 2.066 sec
            Caused an ERROR Address already in use
    voldemort.VoldemortException: Address already in use
    	at voldemort.server.niosocket.NioSocketService.startInner(
    	at voldemort.server.AbstractService.start(
    	at voldemort.server.VoldemortServer.startInner(
    	at voldemort.server.AbstractService.start(
    	at voldemort.ServerTestUtils.startVoldemortServer(
    	at voldemort.utils.ServerTestUtilsTest.setUp(
    Caused by: Address already in use
    	at Method)
    	at voldemort.server.niosocket.NioSocketService.startInner(
Commits on Oct 15, 2012
  1. - Refactored schema check method

    abh1nay committed Oct 15, 2012
    - added fix to the verioned serializer to support writing of objects
      created using the old schema