Cannot erase old /opt/cloudera/parcels

[#1]

Hello,

We have problems with parcels in our PROD cluster (CDP Runtime 7.1.7), we tried to remove old parcels (CDH 6.3.3, CFM 1.0.1.0, CFM 1.1.0.0) on host dallas20
- After the manual delete, Cloudera Manager still shows some parcels with status Distributed.
- The parcel folders on disk are not correct now, probably because of the manual cleanup.
- Also, the cluster is slow and some services presents an error like this in Parcels tab on CM:
Error when distributing to dallas20.metromadrid.net: [Errno 20] Not a directory: /opt/cloudera/parcels/STREAMS_MESSAGING_MANAGER-2.1.0.2.0.1.0-2/meta/parcel.json
We need help with these points:
How can we clean the old parcels in a safe way so CM shows the correct status?
How to fix the error [Errno 20 Not a directory] and make parcel distribution work again?
Is there a supported procedure to reset parcel states in Cloudera Manager?

This problem is blocking us to free space in /opt/cloudera/parcels/ and manage parcels normally.

We are using CDP 7.1.7 (which is programmed to be upgraded at the end of semester) and CM 7.6.7.

Kind regards, Leidy

[#2 · Accepted solution]

Hello @Leidy 

Thank you for reaching out to cloudera

Could you try the below steps

• Stop CM Agent

• Remove the parcels form /opt/cloudera/parcel-repo directory on CM node

• Remove broken parcel dirs & symlinks under /opt/cloudera/parcels/

• Clear parcel cache & .flood staging

• Ensure that on CM UI old parcles links are not present under CM UI >> Parcels >> Parcel configurations

• Restart Agent & CM Server

• Resync via CM UI → “Check for new parcels”

Let me know how it goes

[#3 · Accepted solution]

Hello @Leidy 

Thank you for reaching out to cloudera

Could you try the below steps

• Stop CM Agent

• Remove the parcels form /opt/cloudera/parcel-repo directory on CM node

• Remove broken parcel dirs & symlinks under /opt/cloudera/parcels/

• Clear parcel cache & .flood staging

• Ensure that on CM UI old parcles links are not present under CM UI >> Parcels >> Parcel configurations

• Restart Agent & CM Server

• Resync via CM UI → “Check for new parcels”

Let me know how it goes

[#4]

Hello! 

Thank you very much for your answer and suggestions, in particular, this one was the main reason we were facing issues:
"Clear parcel cache & .flood staging"

After clear them all, everything start to work as well as usual

Kind regards, Leidy

[#5 · Accepted solution]

@Leidy Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.

[#6]

Hola Diana

Sí, muchísimas gracias y disculpa las molestias por no haber contestado anteriormente.

Saludos cordiales, Leidy