[SLIDER-706] application installation failure does not result in clear failure indication

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Slider 0.60
• Fix Version/s: Slider 0.70

Environment

Windows

• Assignee: Steve Loughran
• Reporter: Jonathan Maron
• Created: 09/Dec/14 17:27
• Updated: 11/Mar/15 20:13
• Resolved: 06/Feb/15 16:43

Description

Though an HBase deployment on a windows secure cluster results in a failure to install, the application master and application remain running with no attempts to restart the failed container etc. The app master log does seem to indicate the failure:

2014-12-09 09:07:11,548 [973031640@qtp-618337492-7] DEBUG agent.AgentProviderService (AgentProviderService.java:handleHeartBeat(649)) - Handling heartbeat: HeartBeat{responseId=6, timestamp=1418144831565, hostname='container_1418069434921_0004_01_000003___HBASE_REGIONSERVER', reports=[CommandReport

{role='HBASE_REGIONSERVER', actionId='10-1', status='FAILED', exitCode=1, clusterName='hbase-test', serviceName='hbase-test', taskId=10, roleCommand=INSTALL, configurationTags=null}

], componentStatus=[], nodeStatus=HostStatus{status=HEALTHY, cause='NONE'}}
2014-12-09 09:07:11,549 [973031640@qtp-618337492-7] INFO agent.AgentProviderService (AgentProviderService.java:handleHeartBeat(698)) - Component operation. Status: FAILED

However, the heartbeats from the given container continue:

2014-12-09 09:07:21,561 [973031640@qtp-618337492-7] DEBUG agent.AgentProviderService (AgentProviderService.java:handleHeartBeat(649)) - Handling heartbeat: HeartBeat{responseId=7, timestamp=1418144841601, hostname='container_1418069434921_0004_01_000003___HBASE_REGIONSERVER', reports=[], componentStatus=[], nodeStatus=HostStatus{status=HEALTHY, cause='NONE'}}

Issue Links

• is related to: SLIDER-705 issues extracting application binary packages when resultant path is longer than 260 character limit