Reply
Highlighted
New Contributor
Posts: 2
Registered: ‎08-01-2016

Tracking Config changes made from Cloudera Manager

Hi

 

We have a test cloudera cluster and a Production cluster, using CDH 5.9 enterprise edition. 

We use cloudera manager to make all configuraiton changes to ther services or administration settings. 

 

I would like to keep track of all the changes that we have made in the lower region so that I can check if the same settings have been applied in Prod as well. 

 

or  is there any way I can compare the settings between the lower and Prod region and take appropriate action ? 

 

Please help and let me know in case more information is needed. 

 

New Contributor
Posts: 3
Registered: ‎04-25-2018

Re: Tracking Config changes made from Cloudera Manager

HI Did you find any solution for this problem?

Posts: 1,116
Topics: 1
Kudos: 287
Solutions: 135
Registered: ‎04-22-2014

Re: Tracking Config changes made from Cloudera Manager

@Kmanik,

 

There is no specific feature I know of that does this currently, but it sounds like a good project.

While it takes a bit of manual work, you could leverage the following to do a reasonable job of comparing cluster configurations:

 

http://cm_host:7180/api/v30/cm/deployment?export_redacted

 

NOTE, the api version (/vxx/) that your CM version supports differs depending on the CM version itself.

To find out what the highest API version your CM supports:

 

http://cm_host:7180/api/version

 

This will print out cluster information including configuration.

You could automate this, integrate into versioning, etc.

 

 

New Contributor
Posts: 3
Registered: ‎04-25-2018

Re: Tracking Config changes made from Cloudera Manager

This is what I found out recently. This might be useful. 

 

1. Login to mysql

2. Use scm;

3. select r.REVISION_ID, u.USER_NAME, r,TIMESTAMP, r.MESSAGE from REVISIONS r inner join CONFIGS_AUD c on r.REVISION_ID = c.REV inner join USERS u on r.USER_ID = u.USER_ID;

4. Extract into a report in .csv ( This pulls all information on config change)

5. You can schedule this once a week and tail last 100 lines so that you can keep track of config.

 

Another challenge in this report is unix time needs to be converted into human readable time in this report.