SDP 25.3 is not the latest You're viewing SDP 25.3, not the current release (SDP 26.3).

View HdfsCluster in SDP 26.3 View SDP 26.3 →

Custom resource

HdfsCluster

Auto-generated derived type for HdfsClusterSpec via `CustomResource`

View SDP 25.3 release Download CRD (YAML)

API group: hdfs.stackable.tech
API versions in 25.3: v1alpha1
Scope: Namespaced
Operator: Apache Hadoop HDFS
Roles: 3 (dataNodes, journalNodes, nameNodes)

Schema

HdfsCluster.hdfs.stackable.tech .spec fields for SDP 25.3.

Schema

clusterConfig # object required *
Configuration that applies to all roles and role groups. This includes settings for authentication, logging and the ZooKeeper cluster to use.

Configuration that applies to all roles and role groups. This includes settings for authentication, logging and the ZooKeeper cluster to use.
image # object required *
Specify which image to use, the easiest way is to only configure the productVersion. You can also configure a custom image registry to pull from, as well as completely custom images. Consult the Product image selection documentation for details.

Specify which image to use, the easiest way is to only configure the productVersion. You can also configure a custom image registry to pull from, as well as completely custom images. Consult the Product image selection documentation for details.
dataNodes # role object
This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a key-value-map containing all the roleGroups that are part of this role. Additionally, there is a config, which is configurable at the role and roleGroup level. Everything at roleGroup level is merged on top of what is configured on role level. There is also a second form of config, which can only be configured at role level, the roleConfig. You can learn more about this in the Roles and role group concept documentation.

This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a key-value-map containing all the roleGroups that are part of this role. Additionally, there is a config, which is configurable at the role and roleGroup level. Everything at roleGroup level is merged on top of what is configured on role level. There is also a second form of config, which can only be configured at role level, the roleConfig. You can learn more about this in the Roles and role group concept documentation.
journalNodes # role object
This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a key-value-map containing all the roleGroups that are part of this role. Additionally, there is a config, which is configurable at the role and roleGroup level. Everything at roleGroup level is merged on top of what is configured on role level. There is also a second form of config, which can only be configured at role level, the roleConfig. You can learn more about this in the Roles and role group concept documentation.

This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a key-value-map containing all the roleGroups that are part of this role. Additionally, there is a config, which is configurable at the role and roleGroup level. Everything at roleGroup level is merged on top of what is configured on role level. There is also a second form of config, which can only be configured at role level, the roleConfig. You can learn more about this in the Roles and role group concept documentation.
nameNodes # role object
This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a key-value-map containing all the roleGroups that are part of this role. Additionally, there is a config, which is configurable at the role and roleGroup level. Everything at roleGroup level is merged on top of what is configured on role level. There is also a second form of config, which can only be configured at role level, the roleConfig. You can learn more about this in the Roles and role group concept documentation.

This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a key-value-map containing all the roleGroups that are part of this role. Additionally, there is a config, which is configurable at the role and roleGroup level. Everything at roleGroup level is merged on top of what is configured on role level. There is also a second form of config, which can only be configured at role level, the roleConfig. You can learn more about this in the Roles and role group concept documentation.
clusterOperation # object = {"stopped":false,"reconciliationPaused":false}
Cluster operations properties, allow stopping the product instance as well as pausing reconciliation.

Cluster operations properties, allow stopping the product instance as well as pausing reconciliation.