[jira] [Closed] (AURORA-1873) CuratorServiceGroupMonitor.LOG should use its own logger name
[ https://issues.apache.org/jira/browse/AURORA-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bing-Qian Luan closed AURORA-1873. -- > CuratorServiceGroupMonitor.LOG should use its own logger name > - > > Key: AURORA-1873 > URL: https://issues.apache.org/jira/browse/AURORA-1873 > Project: Aurora > Issue Type: Bug > Components: Scheduler >Reporter: Bing-Qian Luan >Assignee: Bing-Qian Luan >Priority: Trivial > Labels: newbie > Fix For: 0.17.0 > > > CuratorServiceGroupMonitor.LOG should use CuratorServiceGroupMonitor.class as > its logger name (instead of SchedulerMain.class). > Code: > private static final Logger LOG = > LoggerFactory.getLogger(SchedulerMain.class); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AURORA-1878) Increased executor logs can lead to task's running out of disk space
[
https://issues.apache.org/jira/browse/AURORA-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819359#comment-15819359
]
Joshua Cohen commented on AURORA-1878:
--
https://reviews.apache.org/r/55434/
> Increased executor logs can lead to task's running out of disk space
>
>
> Key: AURORA-1878
> URL: https://issues.apache.org/jira/browse/AURORA-1878
> Project: Aurora
> Issue Type: Task
> Components: Executor
>Reporter: Joshua Cohen
>Assignee: Joshua Cohen
>
> After the health check for updates patch, this log statement is being emitted
> once every 500ms:
> https://github.com/apache/aurora/commit/2992c8b4#diff-6d60c873330419a828fb992f46d53372R121
> This is due to this
> [code|https://github.com/apache/aurora/blob/master/src/main/python/apache/aurora/executor/common/status_checker.py#L120-L124]:
> {code}
> if status_result is not None:
> log.info('%s reported %s' % (status_checker.__class__.__name__,
> status_result))
> {code}
> Previously, {{status_result}} would be {{None}} unless the status checker had
> a terminal event. Now, {{status_result}} will always be set, but we only
> consider the {{status_result}} to be terminal if the {{status}} is not
> {{TASK_STARTING}} or {{TASK_RUNNING}}. So, for the healthy case, we log that
> the task is {{TASK_RUNNING}} every 500ms.
> !https://frinkiac.com/meme/S10E02/818984.jpg?b64lines=IFRISVMgV0lMTCBTT1VORCBFVkVSWQogVEhSRUUgU0VDT05EUyBVTkxFU1MKIFNPTUVUSElORyBJU04nVCBPS0FZIQ==!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AURORA-1878) Increased executor logs can lead to task's running out of disk space
[
https://issues.apache.org/jira/browse/AURORA-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Cohen reassigned AURORA-1878:
Assignee: Joshua Cohen
> Increased executor logs can lead to task's running out of disk space
>
>
> Key: AURORA-1878
> URL: https://issues.apache.org/jira/browse/AURORA-1878
> Project: Aurora
> Issue Type: Task
> Components: Executor
>Reporter: Joshua Cohen
>Assignee: Joshua Cohen
>
> After the health check for updates patch, this log statement is being emitted
> once every 500ms:
> https://github.com/apache/aurora/commit/2992c8b4#diff-6d60c873330419a828fb992f46d53372R121
> This is due to this
> [code|https://github.com/apache/aurora/blob/master/src/main/python/apache/aurora/executor/common/status_checker.py#L120-L124]:
> {code}
> if status_result is not None:
> log.info('%s reported %s' % (status_checker.__class__.__name__,
> status_result))
> {code}
> Previously, {{status_result}} would be {{None}} unless the status checker had
> a terminal event. Now, {{status_result}} will always be set, but we only
> consider the {{status_result}} to be terminal if the {{status}} is not
> {{TASK_STARTING}} or {{TASK_RUNNING}}. So, for the healthy case, we log that
> the task is {{TASK_RUNNING}} every 500ms.
> !https://frinkiac.com/meme/S10E02/818984.jpg?b64lines=IFRISVMgV0lMTCBTT1VORCBFVkVSWQogVEhSRUUgU0VDT05EUyBVTkxFU1MKIFNPTUVUSElORyBJU04nVCBPS0FZIQ==!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AURORA-1876) Expose stats on scheduler rate limiter blocking time
[
https://issues.apache.org/jira/browse/AURORA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mehrdad Nurolahzade reassigned AURORA-1876:
---
Assignee: Mehrdad Nurolahzade
> Expose stats on scheduler rate limiter blocking time
>
>
> Key: AURORA-1876
> URL: https://issues.apache.org/jira/browse/AURORA-1876
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
>Reporter: Mehrdad Nurolahzade
>Assignee: Mehrdad Nurolahzade
>Priority: Minor
>
> Scheduler relies on a Guava {{RateLimiter}} to limit the maximum scheduling
> rate (see {{TaskGroups.startGroup()}}). Expose stats on the blocking time
> imposed by the rate limiter {{acquire()}} invocations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AURORA-1878) Increased executor logs can lead to task's running out of disk space
Joshua Cohen created AURORA-1878:
Summary: Increased executor logs can lead to task's running out of
disk space
Key: AURORA-1878
URL: https://issues.apache.org/jira/browse/AURORA-1878
Project: Aurora
Issue Type: Task
Components: Executor
Reporter: Joshua Cohen
After the health check for updates patch, this log statement is being emitted
once every 500ms:
https://github.com/apache/aurora/commit/2992c8b4#diff-6d60c873330419a828fb992f46d53372R121
This is due to this
[code|https://github.com/apache/aurora/blob/master/src/main/python/apache/aurora/executor/common/status_checker.py#L120-L124]:
{code}
if status_result is not None:
log.info('%s reported %s' % (status_checker.__class__.__name__,
status_result))
{code}
Previously, {{status_result}} would be {{None}} unless the status checker had a
terminal event. Now, {{status_result}} will always be set, but we only consider
the {{status_result}} to be terminal if the {{status}} is not {{TASK_STARTING}}
or {{TASK_RUNNING}}. So, for the healthy case, we log that the task is
{{TASK_RUNNING}} every 500ms.
!https://frinkiac.com/meme/S10E02/818984.jpg?b64lines=IFRISVMgV0lMTCBTT1VORCBFVkVSWQogVEhSRUUgU0VDT05EUyBVTkxFU1MKIFNPTUVUSElORyBJU04nVCBPS0FZIQ==!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AURORA-1873) CuratorServiceGroupMonitor.LOG should use its own logger name
[ https://issues.apache.org/jira/browse/AURORA-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817785#comment-15817785 ] Bing-Qian Luan commented on AURORA-1873: Thanks all. Review request submitted: https://reviews.apache.org/r/55409/ > CuratorServiceGroupMonitor.LOG should use its own logger name > - > > Key: AURORA-1873 > URL: https://issues.apache.org/jira/browse/AURORA-1873 > Project: Aurora > Issue Type: Bug > Components: Scheduler >Reporter: Bing-Qian Luan >Assignee: Bing-Qian Luan >Priority: Trivial > Labels: newbie > > CuratorServiceGroupMonitor.LOG should use CuratorServiceGroupMonitor.class as > its logger name (instead of SchedulerMain.class). > Code: > private static final Logger LOG = > LoggerFactory.getLogger(SchedulerMain.class); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AURORA-1873) CuratorServiceGroupMonitor.LOG should use its own logger name
[ https://issues.apache.org/jira/browse/AURORA-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bing-Qian Luan reassigned AURORA-1873: -- Assignee: Bing-Qian Luan > CuratorServiceGroupMonitor.LOG should use its own logger name > - > > Key: AURORA-1873 > URL: https://issues.apache.org/jira/browse/AURORA-1873 > Project: Aurora > Issue Type: Bug > Components: Scheduler >Reporter: Bing-Qian Luan >Assignee: Bing-Qian Luan >Priority: Trivial > Labels: newbie > > CuratorServiceGroupMonitor.LOG should use CuratorServiceGroupMonitor.class as > its logger name (instead of SchedulerMain.class). > Code: > private static final Logger LOG = > LoggerFactory.getLogger(SchedulerMain.class); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
