[AMBARI-18413] RecoveryManager may be logging too often

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.5.0
• Component/s: ambari-agent
• Assignee: Nahappan Somasundaram
• Reporter: Nahappan Somasundaram
• Created: 16/Sep/16 17:15
• Updated: 17/Sep/16 20:03
• Resolved: 17/Sep/16 18:07

Description

On a deployed cluster - while deployment is ongoing I noticed:

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.

Then when a component is killed - similarly very frequent logging till it is recovered.

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.

Issue Links

• links to: Review Board