Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Possible Bug in Parcels Directory Setting, or at least very weird behaviour

Highlighted

Possible Bug in Parcels Directory Setting, or at least very weird behaviour

New Contributor

Hi,

 

After some limited testing we think we've identified a bug with the parcels directory setting. It seems that the agents take the second highest setting from the config_aud table in the scm database instead of the highest (which also is the one that is displayed in the UI).

 

This is the current content of the config_aud table and when we do a scm-agent restart it uses the /data/cloudera/cloudera/parcels directory. Not /opt/cloudera/parcels which is the highest one and also the one that is displayed in the CDH management interface.

If we would change back to /data/cloudera/cloudera/parcels the scm-agent will, after restart, revert back to /opt/cloudera/parcels. As you can see we've done it a couple of times to verify our suspicion.

 

This written with no clue of what these tables actually are but it's the only table where we could find the relevant setting, it also gets written to as soon as we change the value in the interface.

config_id | rev | revtype | attr | value

 

-----------+-----+---------+-------------------+----------------------------------
303 | 212 | 1 | parcels_directory | /opt/cloudera/parcels
303 | 211 | 1 | parcels_directory | /data/cloudera/cloudera/parcels
303 | 210 | 1 | parcels_directory | /opt/cloudera/parcels
303 | 209 | 1 | parcels_directory | /data/cloudera/cloudera/parcels
303 | 208 | 1 | parcels_directory | /data/cloudera/cloudera/parcels
303 | 207 | 1 | parcels_directory | /data/cloudera/cloudera/parcels
303 | 206 | 1 | parcels_directory | /opt/cloudera/parcels
303 | 205 | 0 | parcels_directory | /data/cloudera/cloudera/parcels
302 | 204 | 2 | parcels_directory | /data/cloudera/cloudera/parcels
302 | 203 | 0 | parcels_directory | /data/cloudera/cloudera/parcels
295 | 202 | 2 | parcels_directory | /data/cloudera/cloudera/parcels
295 | 187 | 1 | parcels_directory | /data/cloudera/cloudera/parcels
295 | 186 | 0 | parcels_directory | /data/cloudera/parcels

 

BR

2 REPLIES 2
Highlighted

Re: Possible Bug in Parcels Directory Setting, or at least very weird behaviour

New Contributor

Oh, and we're using latest Cloudera Manager version (cant find actual version).

Re: Possible Bug in Parcels Directory Setting, or at least very weird behaviour

Expert Contributor

Hi, 

 

There are two possible locations to set the parcel_dir property: 1) the agent config.ini file directly [1], and then the in-CM property for setting Parcel Directory [2].

 

You may be seeing this behavior as result of already having a configuration for the parcel dir in /etc/cloudera-scm-agent/config.ini on all your nodes. If configured, this setting takes precedence over any value you set in the UI for the "Parcel Directory" property.

 

Perhaps there's just a discrepancy between the two in your environment?

 

 

[1] - http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_ag_agent_config.html...

 

[2] - http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_ig_parcels.html?scro... bullet #3 "The setting of the parcel_dir property in the Cloudera Manager Agent configuration file overrides this setting."

 

Regards,

--

Mark

Don't have an account?
Coming from Hortonworks? Activate your account here