Support Questions

Find answers, ask questions, and share your expertise

"Remote Parcel Repository URLs" is always initialized upon server restart

avatar

Hi

 

We use Cloudera Cluster in the environment without external access outside to the internet,

 

therefore we remove all predefined "Remote Parcel Repository URLs " addresses in CM ( "REMOTE_PARCEL_REPO_URLS" parameter name  ).

 

The problem is that when cloudera-scm-server service is restarted, all URL's are loaded again

 

For example from server log:

 

2015-02-26 17:58:28,919 INFO main:com.cloudera.parcel.components.ParcelManagerImpl: Adding remote parcel repository : http://archive.cloudera.com/spark/parcels/latest/
......

 

We use cloudera-manager-server-5.3.0-1.cm530.p0.166.el6.x86_64 version

 

Is this some kind of bug?

 

Thanks

Gregory

1 ACCEPTED SOLUTION

avatar
Hi Gregory

I presume that the urls added back are among:
http://archive.cloudera.com/accumulo/parcels/1.4/
http://archive.cloudera.com/accumulo-c5/parcels/latest/
http://archive.cloudera.com/sqoop-connectors/parcels/latest/
http://archive.cloudera.com/spark/parcels/latest/

That happens because certain services implemented with the CSD
extension have a parcel repo associated with them, and they are always
re-added on server start up. We will work toward fixing that in a
future release. Sorry for the annoyance.

View solution in original post

4 REPLIES 4

avatar
Hi Greg

Are you able to turn on API debugging and see if the deletion of repos
actually worked? After this, restart CM. If you still see the loading of
archive.cloudera.com please post the log here, maybe using pastebin

Regards,
Gautam Gopalakrishnan

avatar
Hi Gregory

I presume that the urls added back are among:
http://archive.cloudera.com/accumulo/parcels/1.4/
http://archive.cloudera.com/accumulo-c5/parcels/latest/
http://archive.cloudera.com/sqoop-connectors/parcels/latest/
http://archive.cloudera.com/spark/parcels/latest/

That happens because certain services implemented with the CSD
extension have a parcel repo associated with them, and they are always
re-added on server start up. We will work toward fixing that in a
future release. Sorry for the annoyance.

avatar

Thanks for the quick analysis

 

am I able to track this issue according Jira case?

 

I'd like to know which version will fix this issue

 

Thanks

Gregory

avatar
New Contributor

Any update on this topic?