When a system service (metrics, log.saver, explore etc) is stopped, not all the dependent services are stopped

Description

When we stop CDAP master, we stop the system services run as a part of master.

when metrics.processor which is stopped, it stops dependent services
{MetricsCollectionService, MetricsProcessorStatusService, KafkaClientService, ZKClientService, MetricsProcessorService}

we noticed in the logs that all these dependent services were not stopped before terminating the twill runnable.

CDAP FIX VERSIONS
This issue needs to be fixed for:

  • -3.3.0 - DONE-

  • -3.2.1 - DONE-

  • -3.1.3 - DONE-

  • -3.0.6 - DONE-

  • -2.8.3 - DONE-

Release Notes

Fixed an issue about stopping all dependent services when a service is stopped.

Activity

Show:
Shankar Selvam
September 25, 2015, 9:46 AM

This is due to a bug in co.cask.cdap.common.twill.AbstractMasterTwillRunnable, where we don't wait for the future on the services to get started or stopped.

Shankar Selvam
September 25, 2015, 10:08 AM
Poorna Chandra
October 3, 2015, 12:37 PM

This is a critical fix that needs to be back ported to 2.8, 3.0 and 3.1

Shankar Selvam
October 13, 2015, 9:02 AM
Edited
Fixed

Assignee

Shankar Selvam

Reporter

Shankar Selvam

Labels

None

Docs Impact

None

UX Impact

None

Fix versions

Affects versions

Priority

Blocker