hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-7984) Delete registry entries from ZK on ServiceClient stop and clean up stop/destroy behavior
Date Tue, 10 Apr 2018 14:36:00 GMT

     [ https://issues.apache.org/jira/browse/YARN-7984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Billie Rinaldi updated YARN-7984:
---------------------------------
    Description: 
The service records written to the registry are removed by ServiceClient on a destroy call,
but not on a stop call. The service AM does have some code to clean up the registry entries
when component instances are stopped, but if the AM is killed before it has a chance to perform
the cleanup, these entries will be left in ZooKeeper. It would be better to clean these up
in the stop call, so that RegistryDNS does not provide lookups for containers that don't exist.

Additional stop/destroy behavior improvements include fixing errors / unexpected behavior
related to:
* destroying a saved (not launched or started) service
* destroying a stopped service
* destroying a destroyed service
* returning proper exit codes for destroy failures
* performing other client operations on saved services (fixing NPEs)

  was:
The service records written to the registry are removed by ServiceClient on a destroy call,
but not on a stop call. The service AM does have some code to clean up the registry entries
when component instances are stopped, but if the AM is killed before it has a chance to perform
the cleanup, these entries will be left in ZooKeeper. It would be better to clean these up
in the stop call, so that RegistryDNS does not provide lookups for containers that don't exist.

Additional stop/destroy behavior improvements include:
* destroying a saved (not launched or started) service
* destroying a stopped service
* destroying a destroyed service
* 


> Delete registry entries from ZK on ServiceClient stop and clean up stop/destroy behavior
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-7984
>                 URL: https://issues.apache.org/jira/browse/YARN-7984
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn-native-services
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>            Priority: Critical
>         Attachments: YARN-7984.1.patch, YARN-7984.2.patch
>
>
> The service records written to the registry are removed by ServiceClient on a destroy
call, but not on a stop call. The service AM does have some code to clean up the registry
entries when component instances are stopped, but if the AM is killed before it has a chance
to perform the cleanup, these entries will be left in ZooKeeper. It would be better to clean
these up in the stop call, so that RegistryDNS does not provide lookups for containers that
don't exist.
> Additional stop/destroy behavior improvements include fixing errors / unexpected behavior
related to:
> * destroying a saved (not launched or started) service
> * destroying a stopped service
> * destroying a destroyed service
> * returning proper exit codes for destroy failures
> * performing other client operations on saved services (fixing NPEs)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message