commit 3b419aa6e2
Author: Teemu Ollakka <teemu.ollakka@galeracluster.com>
Date: Sun Feb 19 10:29:34 2023 +0200
Skip fetching config options if provider not loaded via wsrep-API
commit 044220cc06
Author: Teemu Ollakka <teemu.ollakka@galeracluster.com>
Date: Wed Jul 13 10:31:03 2022 +0300
Operation context pointer for client state
commit eeb05a9238
Author: Teemu Ollakka <teemu.ollakka@galeracluster.com>
Date: Mon Jul 4 09:03:23 2022 +0300
Add unit test log in gitignore
commit 92a04070fc
Author: Teemu Ollakka <teemu.ollakka@galeracluster.com>
Date: Sun May 8 12:45:36 2022 +0300
Added convenience method prev() to seqno
commit f83ca1917e
Author: Teemu Ollakka <teemu.ollakka@galeracluster.com>
Date: Sun May 1 16:37:24 2022 +0300
Pass victim context for provider on BF abort
This change is needed for custom provider implementations to
have a way to access the victim in the application context.
Helper interface operation_context to pass caller context for
service/provider callbacks in more type safe way.
commit 244eabe8cf
Author: Teemu Ollakka <teemu.ollakka@galeracluster.com>
Date: Wed May 25 07:39:43 2022 +0300
Handle disconnecting state in on_sync()
When disconnecting from the group, the sync event from the
provider must not change the state back to synced.
commit ba8e23df0d
Author: Teemu Ollakka <teemu.ollakka@galeracluster.com>
Date: Tue Mar 22 17:43:52 2022 +0200
Add provider position field to ws_meta and view
Provider position is needed in coordinated recovery
between application and provider. Pass the position
info from provider to application to allow making
it durable.
commit 53e60f64c9
Author: Teemu Ollakka <teemu.ollakka@galeracluster.com>
Date: Sat Mar 19 14:45:57 2022 +0200
Reset TOI meta after releasing total order in provider
This is to keep the TOI meta available in case the provider
implementation needs it.
commit bccb9997f2
Author: Teemu Ollakka <teemu.ollakka@galeracluster.com>
Date: Mon Jan 3 11:19:58 2022 +0200
Fixed id ostream operator to print human readable ids
commit 6d0b37daaf
Author: Teemu Ollakka <teemu.ollakka@galeracluster.com>
Date: Wed Dec 15 16:37:45 2021 +0200
Silence unused variable warning
commit 4b8616f3d1
Author: Denis Protivensky <denis.protivensky@galeracluster.com>
Date: Wed Dec 15 16:43:31 2021 +0300
Fix provider loading in test for release builds
commit 6df17812d9
Author: Denis Protivensky <denis.protivensky@galeracluster.com>
Date: Tue Dec 14 20:28:56 2021 +0300
Introduce set_provider_factory() method for server_state
This allows injecting an application allocated provider into
server_state.
After this virtual provider getter is unnecessary. Made the getter
normal method and fixed unit tests accordingly.
When the donor lost its donor state during SST due to cluster
partitioning, the state was erranously changed to `s_joined`
in `start_sst()` and `sst_sent()`, which caused assertion failures
in state checking.
Fixed by changing state to `s_joined` only if donor is still in
`s_donor` state.
Use pointers to pass state objects to service constructors
to work around GCC 12 warning
error: member ‘wsrep::mock_storage_service::client_state_’
is used uninitialized
Changed server_state public methods sst_received() and wait_until_state()
to report errors as return value instead of throwing exceptions.
This was done to gradually get rid of public methods which report
errors via exceptions.
This change was part of MDEV-30419.
This patch introduces a queue to store ids of transactions that failed
to send a rollback fragment in streaming_rollback(). This is to avoid
potentially missed rollback fragments when a cluster splits and then
later reforms. Rollback fragments would be missing if a node rolled
back a transaction locally (either BFed or voluntary rollback) while
non-primary, and the attempt to send rollback fragment failed in
transaction::streaming_rollback().
Transaction that fail to send rollback fragment can proceed to
rollback locally. However we must ensure that rollback fragments for
those transactions are eventually delivered by the cluster. This must
be done before a potentially conflicting writeset causes BF-BF
conflicts in the rest of the cluster.
Shutting down the provider may cause replication/appling failures, which
may further result to disconnect calls from failing operations.
Allow concurrent disconnect requests to deal with such a situations.
- populate and pass real error description buffer to provider in case
of applying error
- return 0 from server_state::on_apply() if error voting confirmed
consistency
- remove fragments and rollback after fragment applying failure
- always release streaming applier on commit or rollback
In general the position where the storage recovers after a SST
cannot be known untile the recovery process is over. This in turn
means that the position cannot be known when the server_state
sst_received() method is called. Worked around the problem by
introducing get_position() method into server service which
can be used to get the position from stable storage after SST
has completed and the state has been recovered.
Init first join crashed in
server: s1 unallowed state transition: joined -> joined
This was due to missing state check for state in on_primary_view()
before changing to joined state. Added appropriate check.
Implemented unit tests for simple IST scenarios.
Replaced all references to provider_ in server_state methods to
provider() call which is virtual and can be overridden by test classes.
Provider pointer may not be initialized during unit tests yet.
Transition joiner - disconnecting may happen when the joiner failed
to receive SST succesfully. Because the system is at undefined state
at this point, skip most of the processing in sst_received()
and return control to caller after notifying the provider about
failure.
Transition from server_state connected state to disconnecting must
be allowed to deal with errors during server startup.
Added SST first test cases for server_state transitions:
* Successful join via SST
* Error in connect state
* Error in joiner state
it on disconnect.
- Don't rely on own index from the view because the view may come from
another member (IST/SST), instead always determine own index from own ID.
Refs codership/wsrep-lib#13
SR tranasctions are BF aborted or rolled back on primary view
changes according to the following rules:
* Ongoing local SR transactions are BF aborted if the processing
server is not found from the current view.
* All remote SR transactions whose origin server is not included in the
current view are rolled back.
Depending on the DBMS client session allocation strategy the
client id may or may not be available when the client_session
is constructed, therefore there should be a method to assign
an id after construction. Close/cleanup methods were added to
clean up open transactions appropriately.
