Comment 2 for bug 1197898
Revision history for this message
| Jay Janssen (jay-janssen) wrote Re: [Bug 1197898] Grastate should be zeroed only on Replication errors | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
On Jul 9, 2013, at 1:46 PM, Raghavendra D Prabhu <email address hidden> wrote:
> This is likely a duplicate of lp:1111706
>
This is a super-set of lp:1111706.
> However, before doing so, there is this question:
>
> Would it be fine if there is an option which can be used to force
> galera to not consider grastate.dat for that particular startup,
The option already exists to ignore the grastate.dat: rm -f /var/lib/
My issue is that wsrep abort zeroes the grastate and wsrep aborts are way too common -- I'm not sure what an option to ignore the grastate has to do with that.
> thus
> relying on co-ordinates of wsrep-recover only. (and grastate.dat
> will be created subsequently by galera).
>
grastate.dat is not overwritten by wsrep-recover currently unless the grastate is non-zeroed and the seqno is -1. If you fix that as well, then this may be a better option.
> It can be like --skip-grastate and providing that option would
> imply that DBA knows what he is doing when providing it.
>
> So, this will mean that even if grastate.dat is corrupted, zeroed,
> lost/deleted etc. a full SST can be avoided for that node upon
> examination (examination to ensure that other things like RBR error etc.
> are not there).
This would still be a manual step to override a zeroed grastate. I guess that's my main concern.
Jay Janssen, MySQL Consulting Lead, Percona
http://