wsrep_sst_mysqldump error handling defective

Bug #1285883 reported by Daniel Black
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
New
Undecided
Unassigned

Bug Description

Line 120:

    || echo "SST failed to complete;") | $MYSQL

Piping "SST failed to complete" into the mysql process isn't very useful.

Revision history for this message
Alex Yurchenko (ayurchen) wrote :

But it gives you some idea about what is going on and aborts the client. Not very useful, but what "use" there can be in such a situation?

Revision history for this message
Daniel Black (daniel-black) wrote :

using wsrep_log_error to make it go to standard error and ensure that an exit code is returned

RC=0
MYRC=0
(echo $STOP_WSREP .......
|| RC=$? ) | $MYSQL || MYRC=$?
if [ "$MYRC" -ne 0 ]; then
wsrep_log_error "mysql failed with error $MYRC"
exit $MYRC
fi
if [ "$RC" -ne 0 ]; then
wsrep_log_error "mysqldump failed with error $RC"
exit $RC
fi

I'm assuming stderr is part of the sst interface and something useful happens to it? Didn't see it documented however: http://www.codership.com/wiki/doku.php?id=scriptable_state_snapshot_transfer

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.