Add wsrep state setting and retrieving functions to the API

Bug #506086 reported by Alex Yurchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wsrep API
Status tracked in Trunk
Trunk
Fix Released
Medium
Teemu Ollakka

Bug Description

We already have some important state values: history uuid, seqno and certification index. The list will grow. We need a means to pass this state to a joining node together with the application state.
Blueprint: https://blueprints.launchpad.net/wsrep/+spec/wsrep-state-api

Changed in wsrep:
assignee: nobody → Alex Yurchenko (ayurchen)
importance: Undecided → Medium
milestone: none → 0.8
Revision history for this message
Teemu Ollakka (teemu-ollakka) wrote :

Fix committed in: http://bazaar.launchpad.net/~codership/wsrep/trunk/revision/29

Note that instead of separate API calls to get and set state, state is passed via view and sst callbacks.

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

Other bug subscribers

Related blueprints

Remote bug watches

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