[ 
https://issues.apache.org/jira/browse/YARN-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426288#comment-15426288
 ] 

Varun Saxena commented on YARN-3649:
------------------------------------

In my personal opinion, default values should be such that they can be directly 
used on a production cluster until and unless they depend on deployment i.e. 
network, queue config, which feature to enable/disable, etc.
Or some config which you know, works well for your deployment. Config change 
should be minimum once the feature is enabled.

Take for instance, {{yarn.nodemanager.delete.debug-delay.sec}}. This is mainly 
a debug config to be used in a non production cluster. But default value for it 
is 0.

As ours is an alpha quality feature release, dev makes sense in the short term 
but prod might make more sense in the longer term IMO.
Let us see what others think of it.

BTW, you have missed the test class in the latest patch.
Other than that patch at a high level looks fine.

> Allow configurable prefix for hbase table names (like prod, exp, test etc)
> --------------------------------------------------------------------------
>
>                 Key: YARN-3649
>                 URL: https://issues.apache.org/jira/browse/YARN-3649
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Vrushali C
>            Assignee: Vrushali C
>              Labels: YARN-5355
>         Attachments: YARN-3649-YARN-2928.01.patch, 
> YARN-3649-YARN-5355.002.patch, YARN-3649-YARN-5355.01.patch
>
>
> As per [~jrottinghuis]'s suggestion in YARN-3411, it will be a good idea to 
> have a configurable prefix for hbase table names.  
> This way we can easily run a staging, a test, a production and whatever setup 
> in the same HBase instance / without having to override every single table in 
> the config.
> One could simply overwrite the default prefix and you're off and running.
> For prefix, potential candidates are "tst" "prod" "exp" etc. Once can then 
> still override one tablename if needed, but managing one whole setup will be 
> easier.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to