You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geode.apache.org by "Dave Barnes (JIRA)" <ji...@apache.org> on 2017/03/15 15:35:41 UTC

[jira] [Updated] (GEODE-2664) all gfsh commands that contains log-level needs to be updated to use log4j levels

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

Dave Barnes updated GEODE-2664:
-------------------------------
    Component/s: docs

> all gfsh commands that contains log-level needs to be updated to use log4j levels
> ---------------------------------------------------------------------------------
>
>                 Key: GEODE-2664
>                 URL: https://issues.apache.org/jira/browse/GEODE-2664
>             Project: Geode
>          Issue Type: Bug
>          Components: docs, gfsh
>            Reporter: Jinmei Liao
>
> The commands' auto completion are still giving user options with gemfire log levels, but our logs are mostly using log4j now. We need to have these commands accept log4j levels now. Here are the problems:
> 1. "Export logs" command already accept log4j level, but the auto-complete still hints users with gemfire levels, this is a must fix.
> 2. The auto complete is also used by "start locator", "start server", "alter config", "change log-level" commands, needs to update these commands to accept log4j level as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)