On Aug 24, 2013, at 2:17 PM, Raghavendra D Prabhu <email address hidden> wrote:
> Is the SST fully complete when it is checked with ls?
Yes. The node starts and is in Primary state.
> c) Because of point b and/or due to others, SST may not have occurred
> correctly. Hence the logs are required.
>
I'm not sure what the logs will show you, I've never seen any indication of the tar unpacking in any JOINER logs ever. My simulation was a reasonable situation:
node goes down
table gets dropped
node rejoins with SST
tablespace incorrectly still in place, even after SST and node joins
Reading wsrep_sst_xtrabackup, I don't see any reason why you would think this would even work right. What is in the script that would ensure the JOINER's datadir would get clobbered? The default tar command is simply:
On Aug 24, 2013, at 2:17 PM, Raghavendra D Prabhu <email address hidden> wrote:
> Is the SST fully complete when it is checked with ls?
Yes. The node starts and is in Primary state.
> c) Because of point b and/or due to others, SST may not have occurred
> correctly. Hence the logs are required.
>
I'm not sure what the logs will show you, I've never seen any indication of the tar unpacking in any JOINER logs ever. My simulation was a reasonable situation:
node goes down
table gets dropped
node rejoins with SST
tablespace incorrectly still in place, even after SST and node joins
Reading wsrep_sst_ xtrabackup, I don't see any reason why you would think this would even work right. What is in the script that would ensure the JOINER's datadir would get clobbered? The default tar command is simply:
and -C doesn't stand for "clobber".
Jay Janssen, MySQL Consulting Lead, Percona about.me/ jay.janssen
http://