properties.yaml

version: 0.1.0
spec:
  units:
    - unit: &unitUri
        name: "uri"
        regex: "^(([^:/?#]+):)?(//([^/?#]*))?([^?#]*)(\\?([^#]*))?(#(.*))?"
        examples:
          - "ldap://[2001:db8::7]/c=GB?objectClass?one"
        comment: "Specified in https://tools.ietf.org/html/rfc3986#appendix-B"

properties:
  - property:
      propertyNames:
        - name: "networkaddress.cache.ttl"
          kind:
            type: "file"
            file: "security.properties"
      datatype:
        type: "integer"
        min: "0"
      recommendedValues:
        - fromVersion: "0.0.0"
          value: "30"
      roles:
        - name: "namenode"
          required: true
      asOfVersion: "0.0.0"
      comment: "TTL for successfully resolved domain names."
      description: "TTL for successfully resolved domain names."

  - property:
      propertyNames:
        - name: "networkaddress.cache.ttl"
          kind:
            type: "file"
            file: "security.properties"
      datatype:
        type: "integer"
        min: "0"
      recommendedValues:
        - fromVersion: "0.0.0"
          value: "30"
      roles:
        - name: "datanode"
          required: true
      asOfVersion: "0.0.0"
      comment: "TTL for successfully resolved domain names."
      description: "TTL for successfully resolved domain names."

  - property:
      propertyNames:
        - name: "networkaddress.cache.ttl"
          kind:
            type: "file"
            file: "security.properties"
      datatype:
        type: "integer"
        min: "0"
      recommendedValues:
        - fromVersion: "0.0.0"
          value: "30"
      roles:
        - name: "journalnode"
          required: true
      asOfVersion: "0.0.0"
      comment: "TTL for successfully resolved domain names."
      description: "TTL for successfully resolved domain names."

  - property:
      propertyNames:
        - name: "networkaddress.cache.negative.ttl"
          kind:
            type: "file"
            file: "security.properties"
      datatype:
        type: "integer"
        min: "0"
      recommendedValues:
        - fromVersion: "0.0.0"
          value: "0"
      roles:
        - name: "namenode"
          required: true
      asOfVersion: "0.0.0"
      comment: "TTL for domain names that cannot be resolved."
      description: "TTL for domain names that cannot be resolved."

  - property:
      propertyNames:
        - name: "networkaddress.cache.negative.ttl"
          kind:
            type: "file"
            file: "security.properties"
      datatype:
        type: "integer"
        min: "0"
      recommendedValues:
        - fromVersion: "0.0.0"
          value: "0"
      roles:
        - name: "datanode"
          required: true
      asOfVersion: "0.0.0"
      comment: "TTL for domain names that cannot be resolved."
      description: "TTL for domain names that cannot be resolved."

  - property:
      propertyNames:
        - name: "networkaddress.cache.negative.ttl"
          kind:
            type: "file"
            file: "security.properties"
      datatype:
        type: "integer"
        min: "0"
      recommendedValues:
        - fromVersion: "0.0.0"
          value: "0"
      roles:
        - name: "journalnode"
          required: true
      asOfVersion: "0.0.0"
      comment: "TTL for domain names that cannot be resolved."
      description: "TTL for domain names that cannot be resolved."

  - property:
      propertyNames:
        - name: "dfs.namenode.name.dir"
          kind:
            type: "file"
            file: "hdfs-site.xml"
      datatype:
        type: "string"
        unit: *unitUri
      roles:
        - name: "namenode"
          required: false
        - name: "datanode"
          required: false
      asOfVersion: "0.0.0"
      description: "Determines where on the local filesystem the DFS name node should store the name table(fsimage). If this is a comma-delimited list of directories then the name table is replicated in all of the directories, for redundancy."

  - property:
      propertyNames:
        - name: "dfs.datanode.data.dir"
          kind:
            type: "file"
            file: "hdfs-site.xml"
      datatype:
        type: "string"
        unit: *unitUri
      roles:
        - name: "namenode"
          required: false
        - name: "datanode"
          required: false
      asOfVersion: "0.0.0"
      description: "Determines where on the local filesystem an DFS data node should store its blocks. If this is a comma-delimited list of directories, then data will be stored in all named directories, typically on different devices. Directories that do not exist are ignored."

  - property:
      propertyNames:
        - name: "dfs.replication"
          kind:
            type: "file"
            file: "hdfs-site.xml"
      datatype:
        type: "integer"
        min: "1"
        max: "512"
      defaultValues:
        - fromVersion: "0.0.0"
          value: "3"
      roles:
        - name: "namenode"
          required: true
        - name: "datanode"
          required: true
      asOfVersion: "0.0.0"
      description: "Default block replication. The actual number of replications can be specified when the file is created. The default is used if replication is not specified in create time."

  - property:
      propertyNames:
        - name: "fs.defaultFS"
          kind:
            type: "file"
            file: "core-site.xml"
      datatype:
        type: "string"
        unit: *unitUri
      roles:
        - name: "namenode"
          required: false
        - name: "datanode"
          required: false
      asOfVersion: "0.0.0"
      description: "The name of the default file system. A URI whose scheme and authority determine the FileSystem implementation. The uri's scheme determines the config property (fs.SCHEME.impl) naming the FileSystem implementation class. The uri's authority is used to determine the host, port, etc. for a filesystem."

  - property:
      propertyNames:
        - name: "dfs.namenode.http-address"
          kind:
            type: "file"
            file: "hdfs-site.xml"
      datatype:
        type: "string"
      roles:
        - name: "namenode"
          required: false
      asOfVersion: "0.0.0"
      description: "The address and the base port where the dfs namenode web ui will listen on."

  - property:
      propertyNames:
        - name: "dfs.datanode.ipc.address"
          kind:
            type: "file"
            file: "hdfs-site.xml"
      datatype:
        type: "string"
      roles:
        - name: "datanode"
          required: false
      asOfVersion: "0.0.0"
      description: "The datanode ipc server address and port."

  - property:
      propertyNames:
        - name: "dfs.datanode.address"
          kind:
            type: "file"
            file: "hdfs-site.xml"
      datatype:
        type: "string"
      roles:
        - name: "datanode"
          required: false
      asOfVersion: "0.0.0"
      description: "The datanode server address and port for data transfer."

  - property:
      propertyNames:
        - name: "dfs.datanode.http.address"
          kind:
            type: "file"
            file: "hdfs-site.xml"
      datatype:
        type: "string"
      roles:
        - name: "datanode"
          required: false
      asOfVersion: "0.0.0"
      description: "The datanode http server address and port."

  - property:
      propertyNames:
        - name: "dfs.journalnode.http-address"
          kind:
            type: "file"
            file: "hdfs-site.xml"
      datatype:
        type: "string"
      roles:
        - name: "journalnode"
          required: false
      asOfVersion: "0.0.0"
      description: "The address and port the JournalNode HTTP server listens on. If the port is 0 then the server will start on a free port."

  - property:
      propertyNames:
        - name: "dfs.journalnode.https-address"
          kind:
            type: "file"
            file: "hdfs-site.xml"
      datatype:
        type: "string"
      roles:
        - name: "journalnode"
          required: false
      asOfVersion: "0.0.0"
      description: "The address and port the JournalNode HTTPS server listens on. If the port is 0 then the server will start on a free port."