Le jeudi 29 octobre 2020 à 12:07 +0000, Mekhanikov Denis a écrit : > Hi! > > The issue is that Control Center Agent puts its configuration to the > meta-storage. > Ignite has an issue with processing data in meta-storage with class > that is not present on all nodes: > https://issues.apache.org/jira/browse/IGNITE-13642 > Effectively it means that you can't remove control-center-agent from > a cluster that worked with it previously. > > You have a few options how to solve it: > - Add control-center-agent to class path of all nodes and disable it > using management.sh --off. Classes and configuration will be there, > but it won't do anything. You'll be able to remove the library after > an upgrade to the version that doesn't have this bug. Hopefully, it > will be fixed in Ignite 2.9.1 > > - Remove the metastorage directory from the persistence directory on > all nodes. It will lead to removal of Control Center Agent > configuration along with Baseline Topology history. > You will need to do that together with removal of the control-center- > agent library. > NOTE that removal of metastorage is a dangerous operation and can > lead to data loss. I recommend using the first option if it works for > you. > Make a copy of persistence directories before removing anything. > After the removal and a restart the baseline topology will be reset. > Make sure that first activation will lead to the same BLT like before > the restart to avoid data loss. > Hello,
Thanks for info. I've removed the db directory on all nodes, as most of my data is in 3rd-party storage, and I can live without event logs that uses ignite storage, as we're not in production. We'll keep this in mind to avoid future problems. Regards, -- Bastien Durel DATA Intégration des données de l'entreprise, Systèmes d'information décisionnels. bastien.du...@data.fr tel : +33 (0) 1 57 19 59 28 fax : +33 (0) 1 57 19 59 73 45 avenue Carnot, 94230 CACHAN France www.data.fr
