You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This command should provide equivalent of innotop in perl
To make it standalone we will start a cluster monitor class that listen on localhost and write it's own dataset into directory ./replication-mangager/data of running user.
A cluster configuration file will be produce in file ./replication-mangager/config.toml by default a single server is added into the cluster with current user no password or with user input if any parameters --host --user --password
The client will talk with the new api v3 and can also connect to an existing monitor using parameter monitor-url (default localhost)
From the API processlist of each cluster server can send processlist , explain of a query, variables, status, etc
We could improve the API to return array of per server object when query on a full cluster instead of a single server
The text was updated successfully, but these errors were encountered:
This is motivated by the current issues from mariadb packaging with dependences on perl packages and many different repo that provide mytop possibly a symlink mariadb-top and mariadb-config can be made for foundation. to our tools via a contribution
This command should provide equivalent of innotop in perl
To make it standalone we will start a cluster monitor class that listen on localhost and write it's own dataset into directory ./replication-mangager/data of running user.
A cluster configuration file will be produce in file ./replication-mangager/config.toml by default a single server is added into the cluster with current user no password or with user input if any parameters --host --user --password
The client will talk with the new api v3 and can also connect to an existing monitor using parameter monitor-url (default localhost)
From the API processlist of each cluster server can send processlist , explain of a query, variables, status, etc
We could improve the API to return array of per server object when query on a full cluster instead of a single server
The text was updated successfully, but these errors were encountered: