lib/wsrep-lib
1
0
Fork 0
mirror of https://github.com/codership/wsrep-lib.git synced 2025-07-03 16:22:35 +03:00
Code Activity

Revert "Fix fragment removal on rollback"

Browse Source 
It turns out that avoiding apply error on fragment removal failure, is
not a safe thing to do. If the DBMS restarts, with a entry in the
streaming log storage, it may be recovered by creating a corresponding
streaming applier.

This reverts commit da5098b622.
This commit is contained in:
Daniele Sciascia
2022-01-26 16:50:52 +01:00
parent edd141127c
commit 88c3b2609d
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/server_state.cpp
View File

@ -249,9 +249,9 @@ static int rollback_fragment(wsrep::server_state& server_state,
{
if (remove_fragments)
{
high_priority_service.remove_fragments(ws_meta);
high_priority_service.commit(ws_handle, ws_meta);
high_priority_service.after_apply();
ret = high_priority_service.remove_fragments(ws_meta);
ret = ret || high_priority_service.commit(ws_handle, ws_meta);
ret = ret || (high_priority_service.after_apply(), 0);
}
else
{