Introduces two new vmq-admin commands: disconnect clients and disconnect batch #2181
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Introduces two more vmq-admin commands disconnect clients and disconnect batch.
[
"vmq-admin session disconnect clients client-ids=\n\n",
" Forcefully disconnects a number of clients from the cluster. \n\n",
" --mountpoint=, -m\n",
" specifies the mountpoint, defaults to the default mountpoint\n",
" --cleanup, -c\n",
" removes the stored cluster state of this client like stored\n",
" messages and subscriptions.",
"\n\n"
].
vmq_session_disconnect_batch_usage() ->
[
"vmq-admin session disconnect batch count=Number of clients to be disconnected\n\n",
" Forcefully disconnects a number of (random) clients from the cluster. \n\n",
" --mountpoint=, -m\n",
" specifies the mountpoint, defaults to the default mountpoint\n",
" --cleanup, -c\n",
" removes the stored cluster state of this client like stored\n",
" messages and subscriptions.\n",
" --filter-client-ids=, -f\n"
" the clients will be filterd and not disconnected from the cluster\n",
"\n\n"
Types of Changes
What types of changes does your code introduce to this project?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creatingthe PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.
Further Comments
If this is a relatively large or complex change, kick off the discussion by
explaining why you chose the solution you did and what alternatives you
considered, etc.