AnsweredAssumed Answered

MCS volume low data replication alarms

Question asked by terryhealy on Jun 4, 2018
Latest reply on Jun 9, 2018 by bgajjela

Running V6.0.1 cluster with 20 nodes. Since upgrading, we have numerous volume low data replication alarms in the MCS (Shown below) Replication for the defined volumes ('pcaps', 'tables' in below list) are set to 3, minimum 2. Many of the volumes are local files; In one case ('hd21' below), the node was removed and forgotten, but alarms continue.

 

Why is normal replication not making the necessary copies and resolving these alarms? In the old MCS, for some of these local volumes or 'forgotten' nodes I would have unmounted and deleted them.

 

How can I resolve these?

 

Volume Low Data Replication

 

mapr.hd15.sec.bnl.local.local.logs 1d 4h 46m
mapr.hd21.sec.bnl.local.local.metrics 1d 4h 46m
mapr_home 1d 4h 46m
mapr.cluster.root 1d 4h 46m
mapr.monitoring 1d 4h 46m
mapr.hd21.sec.bnl.local.local.logs 1d 4h 46m
mapr.resourcemanager.volume 5h 14m
mapr.hd21.sec.bnl.local.local.mapred 1d 4h 46m
mapr.hd8.sec.bnl.local.local.metrics 1d 4h 46m
mapr.hd65.sec.bnl.local.local.metrics 1d 4h 46m
tables 1d 4h 46m
mapr.hd3.sec.bnl.local.local.metrics 1d 4h 46m
mapr.monitoring.streams 1d 4h 46m
mapr.hd56.sec.bnl.local.local.metrics 1d 4h 46m
mapr.hd4.sec.bnl.local.local.metrics 1d 4h 46m
pcaps 1d 4h 46m
mapr.hd21.sec.bnl.local.local.audit 1d 4h 46m
mapr.hd18.sec.bnl.local.local.metrics 1d 4h 46m
mapr.hd28.sec.bnl.local.local.metrics 1d 4h 46m
mapr.var 1d 4h 46m
mapr.hd15.sec.bnl.local.local.audit 1d 4h 46m
mapr.hd19.sec.bnl.local.local.metrics 1d 4h 46m
mapr.hd15.sec.bnl.local.local.metrics 1d 4h 46

 

Thanks

Outcomes