You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2016/01/07 19:51:39 UTC

[jira] [Resolved] (AURORA-1413) Wrong help indications of usable constants for the aurora-scheduler's -vlog argument

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

Bill Farner resolved AURORA-1413.
---------------------------------
    Resolution: Fixed

This is effectively being fixed with https://reviews.apache.org/r/41785/, which removes this argument in favor of a more standard java app log configuration.

> Wrong help indications of usable constants for the aurora-scheduler's -vlog argument
> ------------------------------------------------------------------------------------
>
>                 Key: AURORA-1413
>                 URL: https://issues.apache.org/jira/browse/AURORA-1413
>             Project: Aurora
>          Issue Type: Story
>    Affects Versions: 0.10.0
>         Environment: Ubuntu 14.04, OpenJDK8, Mesos 0.22.1. Running inside Docker container.
>            Reporter: Anthony Seure
>            Priority: Minor
>
> The {{aurora-scheduler}}'s help mentions that the available constants for the {{-vlog}} argument must be one _of the constants in java.util.logging.Level_. However, the actual available constants are the ones defined in {{com.twitter.common.logging.RootLogConfig.LogLevel}}.
> Thus, the following logging level constants:
>  - {{ALL}}
>  - {{OFF}}
> are only available in {{java.util.logging.Level}} and make the {{aurora-scheduler}} crash printing the help output if used with the {{-vlog}} option.
> Two possible fixes could be whether to implement the ALL/OFF constants level in {{com.twitter.common.logging.RootLogConfig.LogLevel}} and handle them via the {{-vlog}} argument or replace the mention {{java.util.logging.Level}} from the {{vlog}}'s help with {{com.twitter.common.logging.RootLogConfig.LogLevel}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)