[jira] [Commented] (GEODE-1398) gfsh "alter runtime --member" affects other members in the cluster

["Barbara Pruijn (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379013#comment-16379013 ] 

Barbara Pruijn commented on GEODE-1398:
---------------------------------------

2018 log levels settings:

LogWriter Log4J2
---------------------------------------
SEVERE = FATAL
ERROR = ERROR
WARNING = WARN
INFO, CONFIG = INFO
FINE = DEBUG
FINER, FINEST = TRACE

 

> gfsh "alter runtime --member" affects other members in the cluster
> ------------------------------------------------------------------
>
>                 Key: GEODE-1398
>                 URL: https://issues.apache.org/jira/browse/GEODE-1398
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh
>            Reporter: Swapnil Bawaskar
>            Priority: Major
>
> When altering the runtime to change the log level for a particular member, the 
> gfsh command {{alter runtime --log-level=fine --member=server1}} works as expected, until you start a new member, at which point the new member picks up the altered log-level.
> To reproduce:
> 1. Launch gfsh
> 2. Start a locator
> {{gfsh>start locator --name=loc1}}
> 3. start a server
> {{gfsh>start server --name=server1 --server-port=40404}}
> 4. Alter runtime to change log level to fine:
> {{gfsh>alter runtime --log-level=fine --member=server1}}
> 5. Verify that log level of the locator has not changed.
> 6. Start a second server
> {{gfsh>start server --name=server2 --server-port=40406}}
> 7. see that the new server logs at {{fine}} level.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)