[AMBARI-22087] Druid start component via ambari doesn't wait to check if the component is successfully started

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.6.0
• Fix Version/s: trunk, 3.0.0
• Component/s: ambari-server
• Labels: druid
• Assignee: Nishant Bangarwa
• Reporter: Dileep Kumar Chiguruvada
• Created: 28/Sep/17 17:20
• Updated: 08/Dec/17 21:50

Description

Druid start component via ambari doesn't wait to check if the component is successfully started.

Any component start for Druid service will just execute the start command and comes out with exit status 0. It will not further check if the process is running, or any port if its listening.

say for example Druid Coordinator

2017-09-19 18:48:47,076 - Execute['/usr/lib/jvm/java-openjdk/bin/java -cp /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/druid-coordinator/extensions/mysql-metadata-storage/mysql-connector-java.jar org.apache.ambari.server.DBConnectionVerification 'jdbc:mysql://ctr-e134-1499953498516-160569-01-000007.hwx.site:3306/druid?createDatabaseIfNotExist=true' druid [PROTECTED] com.mysql.jdbc.Driver'] {'tries': 5, 'user': 'druid', 'try_sleep': 10}
2017-09-19 18:48:47,554 - Execute['source /usr/hdp/current/druid-coordinator/conf/druid-env.sh ; /usr/hdp/current/druid-coordinator/bin/node.sh coordinator start'] {'user': 'druid'}

Command completed successfully!

The start command via Ambari-UI shows as passed on Ambari-ops even if the component fails to start. this gives false impression to check the service.