[
https://issues.apache.org/jira/browse/HADOOP-15821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641719#comment-16641719
]
Steve Loughran commented on HADOOP-15821:
-----------------------------------------
thanks for addressing my initial concerns
bq. YarnRegistryAttributes: it mentions YARN entities. It looks like is using
also as generic entities.
PersistencePolicies: it has the concept of app, container, etc. This is used in
the unit tests and around.
This about when to automatically clean stuff up. If the service to clean up
entries in the RM is still in yarn code, it can live there, maybe, or we just
leave as is. It's yarn concepts, yes, but can be ignored elsewhere: it's not
YARN code
> Move Hadoop YARN Registry to Hadoop Registry
> --------------------------------------------
>
> Key: HADOOP-15821
> URL: https://issues.apache.org/jira/browse/HADOOP-15821
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 3.2.0
> Reporter: Íñigo Goiri
> Assignee: Íñigo Goiri
> Priority: Major
> Attachments: HADOOP-15821.000.patch, HADOOP-15821.001.patch,
> HADOOP-15821.002.patch, HADOOP-15821.003.patch, HADOOP-15821.004.patch,
> HADOOP-15821.005.patch, HADOOP-15821.006.patch, HADOOP-15821.007.patch,
> HADOOP-15821.008.patch
>
>
> Currently, Hadoop YARN Registry is in YARN. However, this can be used by
> other parts of the project (e.g., HDFS). In addition, it does not have any
> real dependency to YARN.
> We should move it into commons and make it Hadoop Registry.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
