The other valid comparators are =lt=, =le=, =ge=, and =gt=. They stand for "<", "<=", ">=", ">" respectively. These comparators are only applicable for date time fields.
Only available with Cloudera Manager Enterprise Edition.]]>You must specify at least the hostname and ipAddress in the request objects. If no hostId is specified, it will be set to the hostname. It is an error to try and create host with the same hostId as another host.
]]>You may not change a cluster's CDH version using this API call. Use the "upgradeService" cluster command instead.
To rename the cluster, pass in a json structure that has the new cluster name.
Available since API v2.
]]>Settings that are not listed in the input will maintain their current values.]]>
The license file should be uploaded using a request with content type "multipart/form-data", instead of being encoded into a JSON representation.]]>
Regardless of the list of roles provided in the input data, all management roles are created by this call. The input is used to override any default settings for the specific roles.
This method needs a valid CM license to be installed beforehand.
This method does not start any services or roles.
This method will fail if a CMS instance already exists.
Available role types:
Currently, only updating the rackId is supported. All other fields of the host will be ignored.
]]>The message field contains a description of the error. The causes field, if not null, contains a list of causes for the error.
Note that this never returns an echoMessage. Instead, the result (and all error results) has the above structure.
]]>Cluster Version | Available Service Types |
---|---|
CDH3 | HDFS, MAPREDUCE, HBASE, OOZIE, ZOOKEEPER, HUE |
CDH4 | HDFS, MAPREDUCE, HBASE, OOZIE, ZOOKEEPER, HUE, YARN, IMPALA, FLUME |
Attributes that are not listed in the input will maintain their current values in the configuration.
Only available with Cloudera Manager Enterprise Edition.]]>Attributes that are not listed in the input will maintain their current values in the configuration.
Only available with Cloudera Manager Enterprise Edition.]]>By default, the returned results correspond to a 5 minute window based on the provided end time (which defaults to the current server time). The from and to parameters can be used to control the window being queried. A maximum window of 3 hours is enforced.
When requesting a "full" view, aside from the extended properties of the returned metric data, the collection will also contain information about all metrics available for the role, even if no readings are available in the requested window.
Host metrics also include per-network interface and per-storage device metrics. Since collecting this data incurs in more overhead, query parameters can be used to choose which network interfaces and storage devices to query, or to these metrics altogether.
Storage metrics are collected at different levels; for example, per-disk and per-partition metrics are available. The "storageIds" parameter can be used to filter specific storage IDs.
In the returned data, the network interfaces and storage IDs can be identified by looking at the "context" property of the metric objects.
Only available with Cloudera Manager Enterprise Edition.]]>Available since API v2.
]]>The command will upgrade the services and their configuration to the version available in the CDH4 distribution.]]>
The valid comparators are ==, !=, =lt=, =le=, =ge=, and =gt=. They stand for "==", "!=", "<", "<=", ">=", ">" respectively.]]>
The "full" view contains all available configuration parameters for the service and its role types. This mode performs validation on the configuration, which could take a few seconds on a large cluster (around 500 nodes or more).]]>
Attributes that are not listed in the input will maintain their current values in the configuration.]]>
By default, the returned results correspond to a 5 minute window based on the provided end time (which defaults to the current server time). The from and to parameters can be used to control the window being queried. A maximum window of 3 hours is enforced.
When requesting a "full" view, aside from the extended properties of the returned metric data, the collection will also contain information about all metrics available for the service, even if no readings are available in the requested window.
HDFS services from CDH4 that have more than one nameservice will not expose any metrics. Instead, the nameservices should be queried separately.
Only available with Cloudera Manager Enterprise Edition.]]>Attributes that are not listed in the input will maintain their current values in the configuration.
Only available with Cloudera Manager Enterprise Edition.]]>For HDFS services, the list should contain names of DataNodes to decommission.]]>
The ZooKeeper dependency of the service will not be removed.]]>
As part of disabling HA, any services that depend on the HDFS service being modified will be stopped. The command arguments provide options to re-start these services and to re-deploy the client configurations for services of the cluster after HA has been disabled.]]>
The command will create the needed failover controllers, perform the needed initialization and configuration, and will start the new roles. The existing NameNodes which are part of the nameservice will be re-started in the process.
This process may require changing the service's configuration, to add a dependency on the provided ZooKeeper service. This will be done if such a dependency has not been configured yet, and will cause roles that are not affected by this command to show an "outdated configuration" status.
If a ZooKeeper dependency has already been set up by some other means, it does not need to be provided in the command arguments.]]>
The command will set up the given "active" and "stand-by" NameNodes as an HA pair. Both nodes need to already exist.
If there is a SecondaryNameNode associated with either given NameNode instance, it will be deleted.
Note that while the shared edits path may be different for both nodes, they need to point to the same underlying storage (e.g., an NFS share).
As part of enabling HA, any services that depend on the HDFS service being modified will be stopped. The command arguments provide options to re-start these services and to re-deploy the client configurations for services of the cluster after HA has been enabled.]]>
Available since API v2.
]]>The HA partner must already be formatted and running for this command to run.]]>
Note about high availability: when two NameNodes are working in an HA pair, only one of them should be formatted.
Bulk command operations are not atomic, and may contain partial failures. The returned list will contain references to all successful commands, and a list of error messages identifying the roles on which the command failed.]]>
Only one controller per nameservice needs to be initialized.]]>
The provided role names should reflect one of the NameNodes in the respective HA pair; the role must be stopped and its data directory must already have been formatted. The shared edits directory must be empty for this command to succeed.]]>
This request should be sent to Hue servers only.]]>
For HDFS services, this command should be executed on NameNode roles. It refreshes the NameNode's node list.
For Yarn services, this command should be executed on ResourceManager roles. It refreshes the role's queue and node information.]]>
By default, the returned results correspond to a 5 minute window based on the provided end time (which defaults to the current server time). The from and to parameters can be used to control the window being queried. A maximum window of 3 hours is enforced.
When requesting a "full" view, aside from the extended properties of the returned metric data, the collection will also contain information about all metrics available for the activity, even if no readings are available in the requested window.]]>
By default, the returned results correspond to a 5 minute window based on the provided end time (which defaults to the current server time). The from and to parameters can be used to control the window being queried. A maximum window of 3 hours is enforced.
When requesting a "full" view, aside from the extended properties of the returned metric data, the collection will also contain information about all metrics available, even if no readings are available in the requested window.
Only available with Cloudera Manager Enterprise Edition.]]>Attributes that are not listed in the input will maintain their current values in the configuration.]]>
By default, the returned results correspond to a 5 minute window based on the provided end time (which defaults to the current server time). The from and to parameters can be used to control the window being queried. A maximum window of 3 hours is enforced.
When requesting a "full" view, aside from the extended properties of the returned metric data, the collection will also contain information about all metrics available for the role, even if no readings are available in the requested window.]]>
Log files are returned as plain text (type "text/plain").]]>
Log files are returned as plain text (type "text/plain").]]>
Log files are returned as plain text (type "text/plain").]]>