search for: dbstatist

Folks, thank you for being so helpful. I can't quite figure out the exact command line to get ctdb dbstatistics for the locking.tdb in CSV format. How do you do this? [root at use1-samba-server-c25-use1-01 ec2-user]# ctdb -X --separator=, dbstatistics locking.tdb --help Usage: [OPTION...] -d, --debug=STRING debug level -t, --timelimit=INT timelimit (in seconds) -n, --node=INT...

Hi Bob, On Wed, 11 Nov 2020 08:10:28 -0500, Robert Buck via samba <samba at lists.samba.org> wrote: > Folks, thank you for being so helpful. > > I can't quite figure out the exact command line to get ctdb > dbstatistics for the locking.tdb in CSV format. How do you do this? > > [root at use1-samba-server-c25-use1-01 ec2-user]# ctdb -X --separator=, > dbstatistics locking.tdb --help > > Usage: [OPTION...] > [...] > -Y enable machine readable output > > -x...

...at meltin.net> wrote: > Hi Bob, > > On Wed, 11 Nov 2020 08:10:28 -0500, Robert Buck via samba > <samba at lists.samba.org> wrote: > > > Folks, thank you for being so helpful. > > > > I can't quite figure out the exact command line to get ctdb > > dbstatistics for the locking.tdb in CSV format. How do you do this? > > > > [root at use1-samba-server-c25-use1-01 ec2-user]# ctdb -X --separator=, > > dbstatistics locking.tdb --help > > > > Usage: [OPTION...] > > > [...] > > > -Y enabl...

...igh load). This simple fix will stop an exit from the retry loop on any error. * When updating flags on all nodes, use the correct updated flags. This should avoid wrong flag change messages in the logs. * The recovery daemon will not ban other nodes if the current node is banned. * ctdb dbstatistics command now correctly outputs database statistics. * Fixed a panic with overlapping shutdowns (regression in 2.2). * Fixed 60.ganesha "monitor" event (regression in 2.2). * Fixed a buffer overflow in the "reloadips" implementation. * Fixed segmentation faults in ping_pong...

...single banning credit. This makes a brief failure less likely to cause node to be banned. * ctdb killtcp has been changed to read connections from stdin and 10.interface now uses this feature to improve the time taken to kill connections. * Improvements to hot records statistics in ctdb dbstatistics. * Recovery daemon now assembles up-to-date node flags information from remote nodes before checking if any flags are inconsistent and forcing a recovery. * ctdbd no longer creates multiple lock sub-processes for the same key. This reduces the number of lock sub-processes substantially....

...ef failure less likely to > cause node to be banned. > > * ctdb killtcp has been changed to read connections from stdin and > 10.interface now uses this feature to improve the time taken to kill > connections. > > * Improvements to hot records statistics in ctdb dbstatistics. > > * Recovery daemon now assembles up-to-date node flags information > from remote nodes before checking if any flags are inconsistent and > forcing a recovery. > > * ctdbd no longer creates multiple lock sub-processes for the same > key. This reduces the...