[jira] [Commented] (HBASE-3909) Add dynamic config

["binlijin (JIRA)" <ji...@apache.org>]

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

binlijin commented on HBASE-3909:
---------------------------------

bq. Pardon me. I don't follow. We can't lose the setting of short circuit reads on reload of configs. Do you think this will happen? 
Some configs are hard or not impossible to take effect dynamically right now for example： zookeeper.session.timeout, hbase.regionserver.metahandler.count and so on.
If we want short circuit reads to take effect dynamically we must change HDFS Client.
{code}
DFSClient
  /**
   * DFSClient configuration 
   */
  public static class Conf {
    final boolean useLegacyBlockReader;
    final boolean useLegacyBlockReaderLocal;
    final String domainSocketPath;
    final boolean skipShortCircuitChecksums;
    final int shortCircuitBufferSize;
    final boolean shortCircuitLocalReads;
    final boolean domainSocketDataTraffic;
    final int shortCircuitStreamsCacheSize;
    final long shortCircuitStreamsCacheExpiryMs; 
  }
{code}
[~stack]

> Add dynamic config
> ------------------
>
>                 Key: HBASE-3909
>                 URL: https://issues.apache.org/jira/browse/HBASE-3909
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: stack
>            Assignee: Subbu M Iyer
>         Attachments: 3909-102812.patch, 3909-102912.patch, 3909-v1.patch, 3909.v1, 3909_090712-2.patch, HBASE-3909-backport-from-fb-for-trunk-2.patch, HBASE-3909-backport-from-fb-for-trunk.patch, HBase Cluster Config Details.xlsx, patch-v2.patch, testMasterNoCluster.stack
>
>
> I'm sure this issue exists already, at least as part of the discussion around making online schema edits possible, but no hard this having its own issue.  Ted started a conversation on this topic up on dev and Todd suggested we lookd at how Hadoop did it over in HADOOP-7001



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)