Skip to content

Commit

Permalink
Update doc about possibility to resume ERROR runs
Browse files Browse the repository at this point in the history
  • Loading branch information
Bj0rnen committed May 6, 2015
1 parent 4682701 commit 228381a
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 4 deletions.
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Current version supports running Cassandra cluster repairs in segmented manner,
opportunistically running multiple parallel repairs at the same time on different nodes
within the cluster. Basic repair scheduling functionality is also supported.

Cassandra Reaper does not come with a GUI, but please check
Cassandra Reaper does not come with a GUI, but please check
[this project](https://github.com/spodkowinski/cassandra-reaper-ui) if you'd like to use one.

Please see the [Issues](https://github.com/spotify/cassandra-reaper/issues) section for more
Expand Down Expand Up @@ -202,6 +202,7 @@ Source code for all the REST resources can be found from package com.spotify.rea
* *state*: New value for the state of the repair run.
Possible values for given state are: "PAUSED" or "RUNNING".
* Starts, pauses, or resumes a repair run identified by the "id" path parameter.
* Can also be used to reattempt a repair run in state "ERROR", picking up where it left off.

* DELETE /repair_run/{id}
* Expected query parameters:
Expand Down
6 changes: 3 additions & 3 deletions bin/spreaper
Original file line number Diff line number Diff line change
Expand Up @@ -202,7 +202,7 @@ def _arguments_for_scheduling(parser):

def _arguments_for_resume_repair(parser):
"""Arguments relevant for resuming a repair"""
parser.add_argument("run_id", help="ID of the repair run to resume (or start)")
parser.add_argument("run_id", help="ID of the repair run to resume, start or reattempt")


def _arguments_for_pause_repair(parser):
Expand Down Expand Up @@ -271,7 +271,7 @@ Usage: spreaper [<global_args>] <command> [<command_args>]
schedule Create a repair schedule, choosing the first activation time and days
between repair activations. You need to register a cluster into
Reaper (add-cluster) before calling this.
resume-repair Resume paused repair run (or start a not started one).
resume-repair Resume a paused, start a not started or reattempt a failed repair run.
pause-repair Pause a repair run.
abort-repair Abort a repair run.
start-schedule Resume a paused repair schedule.
Expand Down Expand Up @@ -500,7 +500,7 @@ class ReaperCLI(object):
def resume_repair(self):
reaper, args = ReaperCLI.prepare_reaper(
"resume-repair",
"Resume a paused repair run (or trigger a not started one).",
"Resume a paused, start a not started or reattempt a failed repair run.",
extra_arguments=_arguments_for_resume_repair
)
print "# Resuming a repair run with id: {0}".format(args.run_id)
Expand Down

0 comments on commit 228381a

Please sign in to comment.