aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AURORA-1412) Conflicting `slow_query_log_threshold` arguments for aurora-scheduler
Date Sun, 10 Dec 2017 21:27:00 GMT

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

Stephan Erb resolved AURORA-1412.
---------------------------------
    Resolution: Fixed
      Assignee: Bill Farner

Solved via https://github.com/apache/aurora/commit/94276046606da4e1491ee3d0e0c29cd3649a82e6

> Conflicting `slow_query_log_threshold` arguments for aurora-scheduler
> ---------------------------------------------------------------------
>
>                 Key: AURORA-1412
>                 URL: https://issues.apache.org/jira/browse/AURORA-1412
>             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
>            Assignee: Bill Farner
>            Priority: Minor
>
> When starting the {{aurora-scheduler}}, a WARNING from {{com.twitter.common.args.ArgScanner}}
is yelled. The issue is that the {{slow_query_log_threshold}} option is used to configure
both:
>  - {{org.apache.aurora.scheduler.storage.db.DbModule.slow_query_log_threshold}}
>  - {{org.apache.aurora.scheduler.storage.mem.MemTaskStore.slow_query_log_threshold}}
> Even if the parameter is used to set them both with the same value, this warning should
be avoided by giving explicit and different names for these two options.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message