|
From: 鈴木 幸市 <ko...@in...> - 2014-04-25 01:52:32
|
Did you backup the file you cleared? if not, it was not a good idea to clean things because GTM writes its restart point at its working directory. If you did, then you can restore the file gtm.control back. It is in fact a text file so if you would like, you can edit it for repair. First like is the next GXID value. Following lines define each sequence. This could be a bit harmful but should work. If you ran gtm slave, it will also have gtm.control which can be used as well. Good luck. --- Koichi Suzuki 2014/04/25 2:20、Aaron Jackson <aja...@re...<mailto:aja...@re...>> のメール: So I noticed a problem creating a sequence on my cluster - the logs indicated that there was a gtm failure. The GTM indicated that the sequence existed. So I stopped the GTM but left the two coordinators (and proxies) running. I then wiped out everything exception the configuration file and restarted. Soon after that, I noticed that the schemas I had created were no longer available through the coordinator - through attempts to create them said they existed. The best I can guess is that my reset caused the transaction #s to get munged and the schemas were not visible at the mvcc level I was currently querying. Long story short, I did this one to myself - however, in a real scenario, how would you go about resetting the environment if the GTM suffered a failure and needed to be rebuilt? ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform_______________________________________________ Postgres-xc-general mailing list Pos...@li... https://lists.sourceforge.net/lists/listinfo/postgres-xc-general |