curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CURATOR-114) TestingServer should expose restart() method.
Date Tue, 17 Jun 2014 21:31:23 GMT


ASF GitHub Bot commented on CURATOR-114:

Github user cammckenzie commented on a diff in the pull request:
    --- Diff: curator-test/src/main/java/org/apache/curator/test/ ---
    @@ -104,6 +171,17 @@ public void stop() throws IOException
    +     * Restart the server. This is only valid if the server has previously been
    --- End diff --
    Just following the current convention with the underlying TestingZookeeperServer. It throws
an exception if restart() is called on an instance that is not in a STOPPED state. Are you
suggesting that restart() should work from any state? Or just a LATENT or STOPPED state? Either
way, it would require changes to the TestingZookeeperServer, but I don't think that's inherently
a problem as the restart() method is only used by the TestingCluster, and I don't think modifying
the behaviour would cause issues there.

> TestingServer should expose restart() method.
> ---------------------------------------------
>                 Key: CURATOR-114
>                 URL:
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 2.5.0
>            Reporter: Cameron McKenzie
>            Priority: Trivial
> Currently restarting the TestingServer involves:
> server.stop()
> server = new TestingServer(server.getPort(), server.getTempDirectory());
> The underlying Zookeeper testing server that is contained within TestingServer supports
a restart() method. It would be cleaner to expose this on the TestingServer interface, so
a restart would simply involve:
> server.restart()

This message was sent by Atlassian JIRA

View raw message