Cloudera Manager GUI shows configuration validation when services are created using REST API.

[abhi2Git]

Hi,

I am trying to create services like HDFS, MapReduce in Cloudera Manager using REST API. Services are getting created properly along with configurations, however Cloudera Manager GUI shows configuration validations errors, e.g

1. HDFS Checkpoint Directory: Missing required value: HDFS Checkpoint Directory 2.JobTracker Local Data Directory: Missing required value: JobTracker Local Data Directory. Please see the attached image.

If we call REST GET method for the service configuration, above configurations are set properly.

Please suggest how to get rid of validation errors.

Thanks

Abhijeet

[andyao1]

Hi Abhijeet,

Looks like the HDFS Checkpoint Directory is probably not set on the right entity.

What REST API are you using to query it?

Is it set at the service level or at the Secondary Name Node's role level?

Andrew

On Wed, Jul 31, 2013 at 11:35 PM, Abhijeet Shipure <[email protected]

wrote:

Hi,

I am trying to create services like HDFS, MapReduce in Cloudera Manager using REST API. Services are getting created properly along with configurations, however Cloudera Manager GUI shows configuration validations errors, e.g

1. HDFS Checkpoint Directory: Missing required value: HDFS Checkpoint Directory 2.JobTracker Local Data Directory: Missing required value: JobTracker Local Data Directory. Please see the attached image.

If we call REST GET method for the service configuration, above configurations are set properly.

Please suggest how to get rid of validation errors.

Thanks [image: image]https://f.cloud.github.com/assets/4717153/892041/23922644-fa74-11e2-94b8-501903d28c04.png

Abhijeet

— Reply to this email directly or view it on GitHubhttps://github.com/cloudera/cm_api/issues/3 .

Andrew Yao

Software Engineer Cloudera

[abhi2Git]

Hi Andrew,

As you can see from below given screen shot, the values are already set still Cloudera Manager is showing validation errors :

[EronWright]

I suggest you create a cluster using the UI, then inspect the JSON obtained from the 'deployment' resource (see here). You will notice that some settings are stored at the service level, some at the role group level, and (rarely) at the role level. Your settings appear to be set at the role level, which is atypical.