You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Nahappan Somasundaram (JIRA)" <ji...@apache.org> on 2016/09/16 17:16:20 UTC
[jira] [Created] (AMBARI-18413) RecoveryManager may be logging too
often
Nahappan Somasundaram created AMBARI-18413:
----------------------------------------------
Summary: RecoveryManager may be logging too often
Key: AMBARI-18413
URL: https://issues.apache.org/jira/browse/AMBARI-18413
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.4.0
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
Priority: Critical
Fix For: 2.5.0
On a deployed cluster - while deployment is ongoing I noticed:
{code}
INFO 2016-09-01 17:36:06,381 RecoveryManager.py:255 - NAMENODE needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:36:06,382 RecoveryManager.py:822 - Recovery is paused, likely tasks waiting in pipeline for this host.
INFO 2016-09-01 17:36:07,334 RecoveryManager.py:255 - NAMENODE needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:36:07,334 RecoveryManager.py:822 - Recovery is paused, likely tasks waiting in pipeline for this host.
INFO 2016-09-01 17:36:08,290 RecoveryManager.py:255 - NAMENODE needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:36:08,290 RecoveryManager.py:822 - Recovery is paused, likely tasks waiting in pipeline for this host.
INFO 2016-09-01 17:36:09,247 RecoveryManager.py:255 - NAMENODE needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:36:09,248 RecoveryManager.py:822 - Recovery is paused, likely tasks waiting in pipeline for this host.
INFO 2016-09-01 17:36:10,204 RecoveryManager.py:255 - NAMENODE needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:36:10,204 RecoveryManager.py:822 - Recovery is paused, likely tasks waiting in pipeline for this host.
INFO 2016-09-01 17:36:11,261 RecoveryManager.py:255 - NAMENODE needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:36:11,262 RecoveryManager.py:822 - Recovery is paused, likely tasks waiting in pipeline for this host.
INFO 2016-09-01 17:36:12,214 RecoveryManager.py:255 - NAMENODE needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:36:12,215 RecoveryManager.py:822 - Recovery is paused, likely tasks waiting in pipeline for this host.
INFO 2016-09-01 17:36:13,164 RecoveryManager.py:255 - NAMENODE needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:36:13,165 RecoveryManager.py:822 - Recovery is paused, likely tasks waiting in pipeline for this host.
{code}
Then when a component is killed - similarly very frequent logging till it is recovered.
{code}
INFO 2016-09-01 17:50:44,222 RecoveryManager.py:834 - START command cannot be computed as details are not received from Server.
INFO 2016-09-01 17:50:45,166 RecoveryManager.py:255 - NODEMANAGER needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:50:45,166 RecoveryManager.py:834 - START command cannot be computed as details are not received from Server.
INFO 2016-09-01 17:50:46,111 RecoveryManager.py:255 - NODEMANAGER needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:50:46,111 RecoveryManager.py:834 - START command cannot be computed as details are not received from Server.
INFO 2016-09-01 17:50:47,054 RecoveryManager.py:255 - NODEMANAGER needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:50:47,054 RecoveryManager.py:834 - START command cannot be computed as details are not received from Server.
INFO 2016-09-01 17:50:47,996 RecoveryManager.py:255 - NODEMANAGER needs recovery, desired = STARTED, and current = INSTALLED.
INFO 2016-09-01 17:50:47,997 RecoveryManager.py:834 - START command cannot be computed as details are not received from Server.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)