Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3B6D79C4A for ; Sat, 7 Jan 2012 20:02:23 +0000 (UTC) Received: (qmail 98009 invoked by uid 500); 7 Jan 2012 20:02:20 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 97948 invoked by uid 500); 7 Jan 2012 20:02:19 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 97934 invoked by uid 99); 7 Jan 2012 20:02:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jan 2012 20:02:19 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.220.172] (HELO mail-vx0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jan 2012 20:02:13 +0000 Received: by vcbfk13 with SMTP id fk13so2109553vcb.31 for ; Sat, 07 Jan 2012 12:01:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.221.13.135 with SMTP id pm7mr2891588vcb.51.1325966512216; Sat, 07 Jan 2012 12:01:52 -0800 (PST) Received: by 10.52.29.67 with HTTP; Sat, 7 Jan 2012 12:01:52 -0800 (PST) In-Reply-To: <32608FD6-603A-4CD7-849B-D25A266B0B4B@thelastpickle.com> References: <4EE5517A.9000701@gmail.com> <7633B607-571E-4892-92CB-798358E7E2F1@ecyrd.com> <4EE90ECA.1000708@bnl.gov> <4F076610.4040100@bnl.gov> <4F07849E.3060706@bnl.gov> <32608FD6-603A-4CD7-849B-D25A266B0B4B@thelastpickle.com> Date: Sat, 7 Jan 2012 21:01:52 +0100 Message-ID: Subject: Re: How to find out when a nodetool operation has ended? From: "R. Verlangen" To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec54ee692f1da6d04b5f5a25d X-Virus-Checked: Checked by ClamAV on apache.org --bcaec54ee692f1da6d04b5f5a25d Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable " The repair will continue even if you ctrl+c nodetool, it runs on the server not the client." Hmm, didn't know that. Maybe a tweak for the nodetool that just displays a message after starting: "Started with ..." and some kind of notication (with "wall") when it's done? 2012/1/7 aaron morton > The repair will continue even if you ctrl+c nodetool, it runs on the > server not the client. > > Aside from using ops centre you can also look at TP Stats to see when > there is nothing left in the AntiEntropyStage or look for a log messages > from the StorageService that says=85 > > "Repair command #{} completed successfully" > > Cheers > > ----------------- > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 7/01/2012, at 12:32 PM, Maxim Potekhin wrote: > > Thanks, so I take it there is no solution outside of Opcenter. > > I mean of course I can redirect the output, with additional timestamps if > needed, > to a log file -- which I can access remotely. I just thought there would > be some "status" > command by chance, to tell me what maintenance the node is doing. Too bad > there is not! > > Maxim > > > On 1/6/2012 5:40 PM, R. Verlangen wrote: > > You might consider: > > - installing DataStax OpsCenter ( > http://www.datastax.com/products/opscenter ) > > - starting the repair in a linux screen (so you can attach to the screen > from another location) > > > > > --bcaec54ee692f1da6d04b5f5a25d Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable " The repair will continue even if you ctrl+c =A0nodetool, it run= s on the server not the client."

Hmm, didn't know that. Maybe a tweak for the nod= etool that just displays a message after starting: "Started with ...&q= uot; and some kind of notication (with "wall") when it's done= ?

2012/1/7 aaron morton <aaron@thelastpickle.com>
The repair will continue even if you ct= rl+c =A0nodetool, it runs on the server not the client.=A0

Aside from using ops centre you can also look at TP Stats to see when th= ere is nothing left in the AntiEntropyStage or look for a log messages from= the StorageService that says=85

"Repair command #{} completed successfully"
=A0
Cheers

-----------------
Aaron Morton
Freelance Developer
@aaronmorton=

On 7/01/2012, at 12:32 PM, Maxim Potekhin wrote:

Thanks, so I take it there is no solution outsi= de of Opcenter.

I mean of course I can redirect the output, with add= itional timestamps if needed,
to a log file -- which I can access remotely. I just thought there would be= some "status"
command by chance, to tell me what maintenance = the node is doing. Too bad
there is not!

Maxim


On 1/6/= 2012 5:40 PM, R. Verlangen wrote:
You might consider:
- installing DataStax OpsCenter ( http://www.datastax.com/produc= ts/opscenter )
- starting the repair in a linux scr= een (so you can attach to the screen from another location)



--bcaec54ee692f1da6d04b5f5a25d--