Provider position clutters the public interface and is not
required by wsrep-API v26. Remove the position from ws_meta/view
classes and deal with it internally in custom providers.
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.
The condition to skip changing to `s_joined` for all codepaths
which return from donor state. Extracted the logic into separate
method.
Commented start_sst_action in mock_server_service.
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
After a local certification failure, commit order is released without
the setting the current position in DBMS. Which results in diverging
positions between provider and DBMS, if clean shutdown happens right
after local certification failure.
This patch add method set_position() to server_service class. So that
wsrep-lib can instruct DBMS to set the current position after local
certification failure releases commit order.
- 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
Introduced server_service recover_streaming_appliers() interface
call which will be called in total order whenever streaming appliers
must be recovered. The call comes with two overloads, one which
can be called from client context (e.g. after SST has been received)
and the other from high priority context (e.g. view event handling).
The client context overload should be eventually be deprecated once
there is a mechanism to make provider signal that it has joined to
the cluster and will start applying events.
* Implemented encryption callback and enc_set_key
* Added pure virtual functions for encryption functionality
* Set enc key if provider was not loaded on time
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.
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
When member joins the group and needs to receive an SST it won't
receive the corresponding menbership view event because the SST
happens after the event and will already include the effects of
all events ordered before it. The view then must be recovered from
the received state.
Minor renames and cleanups.
References codership/wsrep-lib#18
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
Unit tests which cause streaming rollback leaked memory because
the streaming applier handle which was created for rollback
fragment handling was not released. Roll back a streaming transaction
and release applier handle appropriately in corresponding tests.
The interface method can be used to notify the DBMS implementation
about state changes in well defined order. The call will be done
under server_state mutex protection.
* Added bootstrap service call to do DBMS side bootstrap operations
during the cluster bootstrap.
* Added last_committed_gtid() to provider interface
* Implemented wait_for_gtid() provider call
* Pass initial position to the server state
* Propagate server max protocol version to provider init options
* Store gtid from connected call to make cluster id and the connect
position available
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.
