[ 
https://issues.apache.org/jira/browse/GEODE-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Barnes reassigned GEODE-10150:
-----------------------------------

    Assignee: Dave Barnes

> alter runtime command and change loglevel command docs bug & improvements
> -------------------------------------------------------------------------
>
>                 Key: GEODE-10150
>                 URL: https://issues.apache.org/jira/browse/GEODE-10150
>             Project: Geode
>          Issue Type: Improvement
>          Components: docs
>    Affects Versions: 1.14.4
>            Reporter: Deepak Khopade
>            Assignee: Dave Barnes
>            Priority: Major
>
> The parameters information for gfsh>alter runtime --log-level shows an 
> incorrect parameter name in a table where all parameter's description is 
> provided. The actual expects --log-level but the row in a table says 
> --loglevel. See the screenshot attached. 
> (https://gemfire.docs.pivotal.io/910/geode/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B)
> Another important point is, we should add a line on both the links below to 
> state the difference when using these commands (alter runtime and change 
> loglevel).
> https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B
> https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/change.html
> When I tried both of these commands, it has been found that for locator we 
> need to use gfsh>change loglevel --loglevel=config --member=locator and 
> gfsh>alter runtime --log-level for cache server members. The alter runtime 
> --log-level  command doesn't work for Locators. 
> So adding a line or changing an existing line on the docs will help new 
> customers. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to