cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3388) StorageService.setMode() is used inconsistently
Date Tue, 25 Oct 2011 16:12:32 GMT


Sylvain Lebresne updated CASSANDRA-3388:

    Fix Version/s: 1.0.2
> StorageService.setMode() is used inconsistently
> -----------------------------------------------
>                 Key: CASSANDRA-3388
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>            Reporter: Tyler Hobbs
>            Priority: Trivial
>             Fix For: 1.0.2
> {{StorageService.setMode()}}, which ends up setting the OperationMode attribute of the
related mbean, is used inconsistently.  In most places, it's used like "{{setMode("MODE: details")}},
but in a few places, it's used more like a normal log message.
> To make this attribute more usable through JMX, {{setMode()}} should have a signature
like {{setMode(mode, details)}}, where the mode parameter could be an enum (or even just a
string, the main thing is just being consistent).  The OperationMode JMX attribute should
definitely remain a string, though.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message