AnsweredAssumed Answered

Local Volume containers non-local how to solve it?

Question asked by dhariaekta on Jul 28, 2016
Latest reply on Sep 20, 2016 by mufeed

mapr.XXX.local.metrics has the alarm Local Volume containers non-local. I think this is causing the queries to take double time to process now.

 

Steps I took:

1) I just restarted warden. It did not work.

2) On test cluster I deleted the volume metrics of a node and restarted the cluster. The volume remained unmounted. I am not able to remount it. If I try mounting it, it says the volume already exists. If I use unmount force, it says already unmounted.

 

 

Is there any good documentation or correct steps to follow to remove the alarm as well as remount a volume?

Outcomes