Hello @dutras    As the Issue has been resolved via Support Case, We are marking the Post as resolved.    For reference, this Case required Repair & associated Steps, which are verbose to be documented in Community. For anyone facing such issues, Kindly submit a Support Case.   Regards, Smarak ... View more

Hello @AzfarB    Thanks for using Cloudera Community. Based on the Post, Your Team observed Solr-Infra JVM reporting WARNING for Swap Space more than 200MB being utilised. Restarting the Solr-Infra JVM ensured the WARNING went away.    Note that Swapping isn't Bad in general & the same has been discussed in detail by Community in [1] & [2]. Plus, Deleting RangerAudits Documents won't affect the same as Solr uses JVM as documented [3]. Indexed Documents aren't persisted in Memory unless Cached, thereby ensuring Deletion won't fix the Swapping guaranteed.    As your Screenshot shows, the Host itself is running short on Memory (~99% Utilised) & Overall Swap is ~80% at ~47GB, out of which Solr-Infra is contributing <1GB. As documented in the below Links, Your Team can focus on the Host Level Usage & Considering Increasing the Swap Threshold from 200MB to at least 10% of the Heap i.e. 2GB for a Warning.   01 additional point can be made as to why Solr-Infra Restart helped resolved the WARNING. This needs to be looked at from the Host perspective as to the amount of Memory freed & Whether the Overall Swap Usage reduced at Host Level after Solr-Infra Restart as opposed to Solr-Infra WARNING being suppressed only.    Regards, Smarak    [1] https://unix.stackexchange.com/questions/2658/why-use-swap-when-there-is-more-than-enough-free-space-in-ram [2] https://chrisdown.name/2018/01/02/in-defence-of-swap.html [3] https://blog.cloudera.com/apache-solr-memory-tuning-for-production/ ... View more

Greetings @melmoumni    Thanks for using Cloudera Community. For now, No to HA for Catalogd. This is coming from the fact stated in [1], wherein the Catalogd Unavailability don't leads to DataLoss & they can be removed to be added on a New Host without any impact. Similarly, the Upstream JIRA [2] remains Unresolved.    Again, I shall keep the Post available for others to provide their feedback, if they have tested the same. In [2], One User share their experience, which doesn't appear to be Successful.    Regards, Smarak   [1] https://impala.apache.org/docs/build/html/topics/impala_proxy.html [2] https://issues.apache.org/jira/browse/IMPALA-2702   ... View more

Hello @grlzz    Thanks for using Cloudera Community. In Summary, the Link shared by your Team [1] is the Way to ensure a Runtime has any Packages installed without the need to have the Packages installed upon CML Job/Model/Experiment Run. Please make a Note of [2] with respect to Limitations, yet from your Post, it appears your Team is already familiar with the same.    We shall mark the Post as Solved. Thank You for your Participation with Cloudera Community.   Regards, Smarak   [1] https://docs.cloudera.com/machine-learning/cloud/runtimes/topics/ml-customized-runtimes.html [2] https://docs.cloudera.com/machine-learning/cloud/runtimes/topics/ml-custom-runtime-limitations.html   ... View more