Hi Jiaju, >> >> >> >> Perhaps, this problem didn't happen before the following commit. >> >> https://github.com/jjzhang/booth/commit/4b00d46480f45a205f2550ff0760c8b372009f7f >> > >> > Currently when all of the initialization (including loading the new >> > ticket information) finished, booth should be regarded as ready. So if >> > you encounter some problem here, I guess we should improve the RA to >> > better reflect the booth startup status, but not moving the >> > initialization order, since it may introduce other regression as we have >> > encountered before;) >> > >> >> I am not still sure which we should fix RA or booth. > > I suggest to add a new function to clear the old ticket info in the CIB, > and call that function when booth just run but before deamonized. So, > before booth_start in the RA returned, the stale data has been cleared. > What do you think about this?;) >
In the case of using cib info, Can you implement it? For example, booth is fail-over on local. Then, booth need to get the ticket in cib. If there is no this problem, I can agree to it. Sincerely, Yuichi -- Yuichi SEINO METROSYSTEMS CORPORATION E-mail:seino.clust...@gmail.com _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
