Support Questions

Find answers, ask questions, and share your expertise

Unable to disable a controller service because of a missing component

avatar
Explorer

Hello,

I have a Controller Service for DistributedMapCacheServer, when i tried to disable it so i can change it's properties, it shows an error of a missing referencing component. Why does my controller service still detects a component that is already deleted and how do i solve this so i can change my controller service properties?

Thanks,

Regards,
Adhitya


InkedCapture_LI.jpg
1 ACCEPTED SOLUTION

avatar
Master Mentor

@Adhitya 

The more detail you can provide the better assistance we may be able to provide here.

1. Can you share the exact HDF, CFM, or Apache NiFi version?
2. Have you searched your NiFi flow configuration History from the NiFi UI --> global menu for that component id to see what history exists for its creation and removal?
3. Have you ever manually edited the flow.xml.gz of flow.json.gz files?
 
While I can not explain from what has been shared how you got in to this state, there are steps to get out of it.

When NiFi is started, it loads the dataflow(s) from the flow.xml.gz or flow.json.gz depending on your NiFi version.  (Basically, if the flow.json.gz exists, then NiFi is using it during startup even though NiFi also writes out the legacy flow.xml.gz still).   So you could shutdown your NiFi and search the flow.xml.gz/flow.json.gz for all occurrences of the ID of the component from shared exception just in case there are other components and not just this DistributedMapCacheClientService still referencing it.   Then delete that reference ID.   I recommend making a backup of the flow.xml.gz and flow.json.gz before any attempts to manually edit these files.    Then start Your NiFi using this modified flow.xml.gz/flow.json.gz file.

Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt



View solution in original post

2 REPLIES 2

avatar
Master Mentor

@Adhitya 

The more detail you can provide the better assistance we may be able to provide here.

1. Can you share the exact HDF, CFM, or Apache NiFi version?
2. Have you searched your NiFi flow configuration History from the NiFi UI --> global menu for that component id to see what history exists for its creation and removal?
3. Have you ever manually edited the flow.xml.gz of flow.json.gz files?
 
While I can not explain from what has been shared how you got in to this state, there are steps to get out of it.

When NiFi is started, it loads the dataflow(s) from the flow.xml.gz or flow.json.gz depending on your NiFi version.  (Basically, if the flow.json.gz exists, then NiFi is using it during startup even though NiFi also writes out the legacy flow.xml.gz still).   So you could shutdown your NiFi and search the flow.xml.gz/flow.json.gz for all occurrences of the ID of the component from shared exception just in case there are other components and not just this DistributedMapCacheClientService still referencing it.   Then delete that reference ID.   I recommend making a backup of the flow.xml.gz and flow.json.gz before any attempts to manually edit these files.    Then start Your NiFi using this modified flow.xml.gz/flow.json.gz file.

Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt



avatar
Community Manager

@Adhitya, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future. 



Regards,

Vidya Sargur,
Community Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community: