[
https://issues.apache.org/jira/browse/AURORA-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Seure updated AURORA-1412:
----------------------------------
Description:
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.
was:
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.
> 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
> 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.3.4#6332)
