-
Notifications
You must be signed in to change notification settings - Fork 588
HDDS-12430. Document the config keys moved from DFSConfigKeysLegacy in ozone-default.xml #7987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
0bf5274
HDDS-12430. Document the config keys moved from DFSConfigKeysLegacy i…
sarvekshayr 3035d74
Remove exceptions from TestOzoneConfigurationFields
sarvekshayr aea5ff0
Deprecate hdds.datanode.data.dir and correct Datanode spelling
sarvekshayr 44ce7e8
Modified dfs.datanode.data.dir
sarvekshayr a440b05
Revert last commit
sarvekshayr 56cd29a
Added HDDS_DATANODE_DIR_KEY in integration failing tests
sarvekshayr 0611217
Fixed checkstyle
sarvekshayr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -171,8 +171,7 @@ | |
| <name>hdds.datanode.dir</name> | ||
| <value/> | ||
| <tag>OZONE, CONTAINER, STORAGE, MANAGEMENT</tag> | ||
| <description>Determines where on the local filesystem HDDS data will be | ||
| stored. Defaults to hdds.datanode.data.dir if not specified. | ||
| <description>Determines where on the local filesystem HDDS data will be stored. | ||
| The directories should be tagged with corresponding storage types | ||
| ([SSD]/[DISK]/[ARCHIVE]/[RAM_DISK]) for storage policies. The default | ||
| storage type will be DISK if the directory does not have a storage type | ||
|
|
@@ -4543,4 +4542,126 @@ | |
| allowing for better identification and analysis of performance issues. | ||
| </description> | ||
| </property> | ||
|
|
||
| <property> | ||
| <name>hdds.datanode.dns.interface</name> | ||
| <value>default</value> | ||
| <tag>OZONE, DATANODE</tag> | ||
| <description> | ||
| The name of the Network Interface from which a Datanode should | ||
| report its IP address. e.g. eth2. This setting may be required for some | ||
| multi-homed nodes where the Datanodes are assigned multiple hostnames | ||
| and it is desirable for the Datanodes to use a non-default hostname. | ||
| </description> | ||
| </property> | ||
| <property> | ||
| <name>hdds.datanode.dns.nameserver</name> | ||
| <value>default</value> | ||
| <tag>OZONE, DATANODE</tag> | ||
| <description> | ||
| The host name or IP address of the name server (DNS) which a Datanode | ||
| should use to determine its own host name. | ||
| </description> | ||
| </property> | ||
| <property> | ||
| <name>hdds.datanode.hostname</name> | ||
| <value/> | ||
| <tag>OZONE, DATANODE</tag> | ||
| <description> | ||
| Optional. The hostname for the Datanode containing this | ||
| configuration file. Will be different for each machine. | ||
| Defaults to current hostname. | ||
| </description> | ||
| </property> | ||
| <property> | ||
| <name>hdds.datanode.use.datanode.hostname</name> | ||
| <value>false</value> | ||
| <tag>OZONE, DATANODE</tag> | ||
| <description> | ||
| Whether Datanodes should use Datanode hostnames when | ||
| connecting to other Datanodes for data transfer. | ||
| </description> | ||
| </property> | ||
| <property> | ||
| <name>hdds.xframe.enabled</name> | ||
| <value>true</value> | ||
| <tag>OZONE, HDDS</tag> | ||
| <description> | ||
| If true, then enables protection against clickjacking by returning | ||
| X_FRAME_OPTIONS header value set to SAMEORIGIN. | ||
| Clickjacking protection prevents an attacker from using transparent or | ||
| opaque layers to trick a user into clicking on a button | ||
| or link on another page. | ||
| </description> | ||
| </property> | ||
| <property> | ||
| <name>hdds.xframe.value</name> | ||
| <value>SAMEORIGIN</value> | ||
| <tag>OZONE, HDDS</tag> | ||
| <description> | ||
| This configration value allows user to specify the value for the | ||
| X-FRAME-OPTIONS. The possible values for this field are | ||
| DENY, SAMEORIGIN and ALLOW-FROM. Any other value will throw an | ||
| exception when Datanodes are starting up. | ||
| </description> | ||
| </property> | ||
| <property> | ||
| <name>hdds.metrics.session-id</name> | ||
| <value/> | ||
| <tag>OZONE, HDDS</tag> | ||
| <description> | ||
| Get the user-specified session identifier. The default is the empty string. | ||
| The session identifier is used to tag metric data that is reported to some | ||
| performance metrics system via the org.apache.hadoop.metrics API. The | ||
| session identifier is intended, in particular, for use by Hadoop-On-Demand | ||
| (HOD) which allocates a virtual Hadoop cluster dynamically and transiently. | ||
| HOD will set the session identifier by modifying the mapred-site.xml file | ||
| before starting the cluster. | ||
| When not running under HOD, this identifer is expected to remain set to | ||
| the empty string. | ||
| </description> | ||
| </property> | ||
| <property> | ||
| <name>hdds.datanode.kerberos.principal</name> | ||
| <value/> | ||
| <tag>OZONE, DATANODE</tag> | ||
| <description> | ||
| The Datanode service principal. This is typically set to | ||
| dn/[email protected]. Each Datanode will substitute _HOST with its | ||
| own fully qualified hostname at startup. The _HOST placeholder | ||
| allows using the same configuration setting on all Datanodes. | ||
| </description> | ||
| </property> | ||
| <property> | ||
| <name>hdds.datanode.kerberos.keytab.file</name> | ||
| <value/> | ||
| <tag>OZONE, DATANODE</tag> | ||
| <description> | ||
| The keytab file used by each Datanode daemon to login as its | ||
| service principal. The principal name is configured with | ||
| hdds.datanode.kerberos.principal. | ||
| </description> | ||
| </property> | ||
| <property> | ||
| <name>hdds.metrics.percentiles.intervals</name> | ||
| <value></value> | ||
| <tag>OZONE, DATANODE</tag> | ||
| <description> | ||
| Comma-delimited set of integers denoting the desired rollover intervals | ||
| (in seconds) for percentile latency metrics on the Datanode. | ||
| By default, percentile latency metrics are disabled. | ||
| </description> | ||
| </property> | ||
|
|
||
| <property> | ||
| <name>net.topology.node.switch.mapping.impl</name> | ||
| <value>org.apache.hadoop.net.ScriptBasedMapping</value> | ||
| <tag>OZONE, SCM</tag> | ||
| <description> | ||
| The default implementation of the DNSToSwitchMapping. It | ||
| invokes a script specified in net.topology.script.file.name to resolve | ||
| node names. If the value for net.topology.script.file.name is not set, the | ||
| default value of DEFAULT_RACK is returned for all node names. | ||
| </description> | ||
| </property> | ||
| </configuration> | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.