You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Eric Yang (JIRA)" <ji...@apache.org> on 2018/08/14 16:24:00 UTC
[jira] [Commented] (YARN-8055) Yarn service: revisit the version in
service
[ https://issues.apache.org/jira/browse/YARN-8055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580023#comment-16580023 ]
Eric Yang commented on YARN-8055:
---------------------------------
For revisiting the versioning strategy, we currently have a version that can be defined as part of yarnfile json. This field can be a product version, or user defined version to trigger upgrade. The product version is vendor supplied information, where user defined version might be used to make configuration changes. Either production version changes, or configuration changes, the version number must be different than previous one to trigger upgrade framework to work. We have two suggested paths to manage version numbers currently. The options are:
# Couple product version with configuration version, similar to Ambari. User is offered a stack version by upstream vendor, but user can customize the suffix of the version number with unique string to make the stack deployment unique.
# Decoupled product version from configuration version. Product version is provided by upstream vendor, and configuration version is internal to ServiceMaster to track history of the configuration changes.
The current implementation is favoring option 1. The benefit of using option 1 is the history tracking is done by external system. Option 2 enables the history tracking to be internal to YARN service, hence it is more self contained.
YARN service is implemented on top of HDFS. It does not have a low latency indexed storage for configuration management. I am inclined to keep option 1 for status quo for the next couple years until low latency indexed K/V pair storage system is available in Hadoop.
> Yarn service: revisit the version in service
> --------------------------------------------
>
> Key: YARN-8055
> URL: https://issues.apache.org/jira/browse/YARN-8055
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Priority: Major
>
> There is a version field added to service with YARN-7523. This version is mandatory.
> There are couple of suggestions related to version:
> 1. make the version optional.
> 2. have a product_version and config_version.
> We need to revisit the version strategy.
--
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