Provide wsrep_locked_seqno in status

Bug #1170886 reported by Raghavendra D Prabhu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Invalid
Low
Raghavendra D Prabhu

Bug Description

It may be useful to have this in output of show status.

Changed in percona-xtradb-cluster:
milestone: none → 5.5.31-25
milestone: 5.5.31-25 → 5.5.30-24.8
assignee: nobody → Raghavendra D Prabhu (raghavendra-prabhu)
status: New → Triaged
Changed in percona-xtradb-cluster:
importance: Undecided → Low
milestone: 5.5.31-24.8 → 5.5.31-25
Revision history for this message
Alex Yurchenko (ayurchen) wrote :

Notice that wsrep_last_committed is pretty much it.

Revision history for this message
Jay Janssen (jay-janssen) wrote :

@Alex: right, I'm unclear why we need another status variable.

@Raghu: what would the difference be between wsrep_last_committed and your proposed variable?

Changed in percona-xtradb-cluster:
milestone: 5.5.33-23.7.6 → future-5.5
Revision history for this message
Krunal Bauskar (krunal-bauskar) wrote :

So there is already a variable that is reflecting the needed info and based on comment there doesn't seems to be a need for a new one. Closing the bug as INVALID.

Changed in percona-xtradb-cluster:
status: Triaged → Invalid
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1136

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.