|
@@ -33,9 +33,11 @@
|
|
|
<property>
|
|
|
<name>dfs.namenode.logging.level</name>
|
|
|
<value>info</value>
|
|
|
- <description>The logging level for dfs namenode. Other values are "dir"(trac
|
|
|
-e namespace mutations), "block"(trace block under/over replications and block
|
|
|
-creations/deletions), or "all".</description>
|
|
|
+ <description>
|
|
|
+ The logging level for dfs namenode. Other values are "dir" (trace
|
|
|
+ namespace mutations), "block" (trace block under/over replications
|
|
|
+ and block creations/deletions), or "all".
|
|
|
+ </description>
|
|
|
</property>
|
|
|
|
|
|
<property>
|
|
@@ -710,4 +712,118 @@ creations/deletions), or "all".</description>
|
|
|
</description>
|
|
|
</property>
|
|
|
|
|
|
+<property>
|
|
|
+ <name>dfs.client.failover.max.attempts</name>
|
|
|
+ <value>15</value>
|
|
|
+ <description>
|
|
|
+ Expert only. The number of client failover attempts that should be
|
|
|
+ made before the failover is considered failed.
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
+<property>
|
|
|
+ <name>dfs.client.failover.sleep.base.millis</name>
|
|
|
+ <value>500</value>
|
|
|
+ <description>
|
|
|
+ Expert only. The time to wait, in milliseconds, between failover
|
|
|
+ attempts increases exponentially as a function of the number of
|
|
|
+ attempts made so far, with a random factor of +/- 50%. This option
|
|
|
+ specifies the base value used in the failover calculation. The
|
|
|
+ first failover will retry immediately. The 2nd failover attempt
|
|
|
+ will delay at least dfs.client.failover.sleep.base.millis
|
|
|
+ milliseconds. And so on.
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
+<property>
|
|
|
+ <name>dfs.client.failover.sleep.max.millis</name>
|
|
|
+ <value>15000</value>
|
|
|
+ <description>
|
|
|
+ Expert only. The time to wait, in milliseconds, between failover
|
|
|
+ attempts increases exponentially as a function of the number of
|
|
|
+ attempts made so far, with a random factor of +/- 50%. This option
|
|
|
+ specifies the maximum value to wait between failovers.
|
|
|
+ Specifically, the time between two failover attempts will not
|
|
|
+ exceed +/- 50% of dfs.client.failover.sleep.max.millis
|
|
|
+ milliseconds.
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
+<property>
|
|
|
+ <name>dfs.client.failover.connection.retries</name>
|
|
|
+ <value>0</value>
|
|
|
+ <description>
|
|
|
+ Expert only. Indicates the number of retries a failover IPC client
|
|
|
+ will make to establish a server connection.
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
+<property>
|
|
|
+ <name>dfs.client.failover.connection.retries.on.timeouts</name>
|
|
|
+ <value>0</value>
|
|
|
+ <description>
|
|
|
+ Expert only. The number of retry attempts a failover IPC client
|
|
|
+ will make on socket timeout when establishing a server connection.
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
+<property>
|
|
|
+ <name>dfs.federation.nameservices</name>
|
|
|
+ <value></value>
|
|
|
+ <description>
|
|
|
+ Comma-separated list of nameservices.
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
+<property>
|
|
|
+ <name>dfs.federation.nameservice.id</name>
|
|
|
+ <value></value>
|
|
|
+ <description>
|
|
|
+ The ID of this nameservice. If the nameservice ID is not
|
|
|
+ configured or more than one nameservice is configured for
|
|
|
+ dfs.federation.nameservices it is determined automatically by
|
|
|
+ matching the local node's address with the configured address.
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
+<property>
|
|
|
+ <name>dfs.ha.namenodes.EXAMPLENAMESERVICE</name>
|
|
|
+ <value></value>
|
|
|
+ <description>
|
|
|
+ The prefix for a given nameservice, contains a comma-separated
|
|
|
+ list of namenodes for a given nameservice (eg EXAMPLENAMESERVICE).
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
+<property>
|
|
|
+ <name>dfs.ha.namenode.id</name>
|
|
|
+ <value></value>
|
|
|
+ <description>
|
|
|
+ The ID of this namenode. If the namenode ID is not configured it
|
|
|
+ is determined automatically by matching the local node's address
|
|
|
+ with the configured address.
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
+<property>
|
|
|
+ <name>dfs.ha.log-roll.period</name>
|
|
|
+ <value>120</value>
|
|
|
+ <description>
|
|
|
+ How often, in seconds, the StandbyNode should ask the active to
|
|
|
+ roll edit logs. Since the StandbyNode only reads from finalized
|
|
|
+ log segments, the StandbyNode will only be as up-to-date as how
|
|
|
+ often the logs are rolled. Note that failover triggers a log roll
|
|
|
+ so the StandbyNode will be up to date before it becomes active.
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
+<property>
|
|
|
+ <name>dfs.ha.tail-edits.period</name>
|
|
|
+ <value>60</value>
|
|
|
+ <description>
|
|
|
+ How often, in seconds, the StandbyNode should check for new
|
|
|
+ finalized log segments in the shared edits log.
|
|
|
+ </description>
|
|
|
+</property>
|
|
|
+
|
|
|
</configuration>
|