2a56aa003d
We use v5 and v5.3.0 to put different python files for CDH5 and CDH5.3.0. CDH5 is CDH5.0.0, we use the name "CDH5" instead of "CDH5.0.0" for backward support. Currently since CDH5.0.0 does not support cm_api>6, we cannot use first_run API in CDH5.0.0, so we only implemented parts of the services that we implemented in CDH5.3.0. implements bp: cdh-version-management Change-Id: I3b3058f25912ddf6206d64db88ac40138a45a53f
110 lines
6.7 KiB
JSON
110 lines
6.7 KiB
JSON
[
|
|
{
|
|
"desc": "When set, Cloudera Manager will send alerts when the health of this service reaches the threshold specified by the EventServer setting eventserver_health_events_alert_threshold",
|
|
"display_name": "Enable Service Level Health Alerts",
|
|
"name": "enable_alerts",
|
|
"value": "true"
|
|
},
|
|
{
|
|
"desc": "The user that this service's processes should run as.",
|
|
"display_name": "System User",
|
|
"name": "process_username",
|
|
"value": "solr"
|
|
},
|
|
{
|
|
"desc": "The group that this service's processes should run as.",
|
|
"display_name": "System Group",
|
|
"name": "process_groupname",
|
|
"value": "solr"
|
|
},
|
|
{
|
|
"desc": "The class to use in Sentry authorization for user to group mapping. Sentry authorization may be configured to use either Hadoop groups or local groups defined in the policy file. When configured with Hadoop groups, Sentry will ask the HDFS Namenode for group mapping for a given user to determine authorization access.",
|
|
"display_name": "Sentry User to Group Mapping Class",
|
|
"name": "solr_sentry_provider",
|
|
"value": "org.apache.sentry.provider.file.HadoopGroupResourceAuthorizationProvider"
|
|
},
|
|
{
|
|
"desc": "Name of the ZooKeeper service that this Search service instance depends on",
|
|
"display_name": "ZooKeeper Service",
|
|
"name": "zookeeper_service",
|
|
"value": null
|
|
},
|
|
{
|
|
"desc": "Choose the authentication mechanism used by Solr.",
|
|
"display_name": "Solr Secure Authentication",
|
|
"name": "solr_security_authentication",
|
|
"value": "simple"
|
|
},
|
|
{
|
|
"desc": "ZooKeeper znode used to store information about this Solr service.",
|
|
"display_name": "ZooKeeper Znode",
|
|
"name": "zookeeper_znode",
|
|
"value": "/solr"
|
|
},
|
|
{
|
|
"desc": "For advanced use only, key-value pairs (one on each line) to be inserted into a role's environment. Applies to configurations of all roles in this service except client configuration.",
|
|
"display_name": "Solr Service Environment Advanced Configuration Snippet (Safety Valve)",
|
|
"name": "solr_env_safety_valve",
|
|
"value": null
|
|
},
|
|
{
|
|
"desc": "When set, Cloudera Manager will send alerts when this entity's configuration changes.",
|
|
"display_name": "Enable Configuration Change Alerts",
|
|
"name": "enable_config_alerts",
|
|
"value": "false"
|
|
},
|
|
{
|
|
"desc": "HDFS directory used for storage by this Solr service.",
|
|
"display_name": "HDFS Data Directory",
|
|
"name": "hdfs_data_dir",
|
|
"value": "/solr"
|
|
},
|
|
{
|
|
"desc": "If Solr does not respond on its web URL within this time interval, the Catalina process is killed.",
|
|
"display_name": "Solrd Watchdog Timeout",
|
|
"name": "solrd_watchdog_timeout",
|
|
"value": "30"
|
|
},
|
|
{
|
|
"desc": "Use Sentry to enable role-based, fine-grained authorization. Sentry is supported only on Search 1.1 or later and CDH 5 or later deployments and requires authentication to be turned on for Solr.</a>.",
|
|
"display_name": "Enable Sentry Authorization",
|
|
"name": "solr_sentry_enabled",
|
|
"value": "false"
|
|
},
|
|
{
|
|
"desc": "HDFS path to the global policy file for Sentry authorization. This should be a relative path (and not a full HDFS URL). The global policy file must be in Sentry policy file format.",
|
|
"display_name": "Sentry Global Policy File",
|
|
"name": "sentry_solr_provider_resource",
|
|
"value": "/user/solr/sentry/sentry-provider.ini"
|
|
},
|
|
{
|
|
"desc": "For advanced use only, a string to be inserted into <strong>sentry-site.xml</strong>. Applies to configurations of all roles in this service except client configuration.",
|
|
"display_name": "Solr Service Advanced Configuration Snippet (Safety Valve) for sentry-site.xml",
|
|
"name": "solr_sentry_safety_valve",
|
|
"value": null
|
|
},
|
|
{
|
|
"desc": "<p>The configured triggers for this service. This is a JSON formatted list of triggers. These triggers are evaluated as part as the health system. Every trigger expression is parsed, and if the trigger condition is met, the list of actions provided in the trigger expression is executed.</p><p>Each trigger has all of the following fields:</p><ul><li><code>triggerName</code> <strong>(mandatory)</strong> - the name of the trigger. This value must be unique for the specific service. </li><li><code>triggerExpression</code> <strong>(mandatory)</strong> - a tsquery expression representing the trigger. </li><li><code>streamThreshold</code> <strong>(optional)</strong> - the maximum number of streams that can satisfy a condition of a trigger before the condition fires. By default set to 0, and any stream returned causes the condition to fire. </li><li><code>enabled</code> <strong> (optional)</strong> - by default set to 'true'. If set to 'false' the trigger will not be evaluated.</li></ul></p><p>For example, here is a JSON formatted trigger that fires if there are more than 10 DataNodes with more than 500 file-descriptors opened:</p><p><pre>[{\"triggerName\": \"sample-trigger\",\n \"triggerExpression\": \"IF (SELECT fd_open WHERE roleType = DataNode and last(fd_open) > 500) DO health:bad\",\n \"streamThreshold\": 10, \"enabled\": \"true\"}]</pre></p><p>Consult the trigger rules documentation for more details on how to write triggers using tsquery.</p><p>The JSON format is evolving and may change in the future and as a result backward compatibility is not guaranteed between releases at this time.</p>",
|
|
"display_name": "Service Triggers",
|
|
"name": "service_triggers",
|
|
"value": "[]"
|
|
},
|
|
{
|
|
"desc": "For advanced use only, a list of derived configuration properties that will be used by the Service Monitor instead of the default ones.",
|
|
"display_name": "Service Monitor Derived Configs Advanced Configuration Snippet (Safety Valve)",
|
|
"name": "smon_derived_configs_safety_valve",
|
|
"value": null
|
|
},
|
|
{
|
|
"desc": "Name of the HDFS service that this Search service instance depends on",
|
|
"display_name": "HDFS Service",
|
|
"name": "hdfs_service",
|
|
"value": null
|
|
},
|
|
{
|
|
"desc": "The health test thresholds of the overall Solr Server health. The check returns \"Concerning\" health if the percentage of \"Healthy\" Solr Servers falls below the warning threshold. The check is unhealthy if the total percentage of \"Healthy\" and \"Concerning\" Solr Servers falls below the critical threshold.",
|
|
"display_name": "Healthy Solr Server Monitoring Thresholds",
|
|
"name": "solr_solr_servers_healthy_thresholds",
|
|
"value": "{\"critical\":\"90.0\",\"warning\":\"95.0\"}"
|
|
}
|
|
] |