Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
In-Reply-To: <55E9939F.5030507@ericsson.com>
References: <55E9939F.5030507@ericsson.com>
Date: Sun, 6 Sep 2015 15:27:17 +0300
Message-ID: 
 <CAEB7=3aDJ0r9gC0NoJ6nk5X0sL-+18qp+HNTvdMjuUUuJMJcmQ@mail.gmail.com>
Subject: Re: Repair documentation
From: Tzach Livyatan <tzach@cloudius-systems.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=e89a8f50355cf2bfc9051f13409c

--e89a8f50355cf2bfc9051f13409c
Content-Type: text/plain; charset=UTF-8

On Fri, Sep 4, 2015 at 3:50 PM, Marcus Olsson <marcus.olsson@ericsson.com>
wrote:

> Hi,
>
> While checking the repair documentation at
> http://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsRepair.html
> I noticed the line *Use the **-hosts** option to list the good nodes to
> use for repairing the bad nodes. Use **-h** to name the bad nodes.* and
> below there was an example:
>
> *nodetool repair -pr -hosts **10.2**.**2.20* *10.2**.**2.21* which should
> do *A partitioner range repair of the bad partition on current node using
> the good partitions on 10.2.2.20 or 10.2.2.21* according to the
> documentation.
>
Look like -pr and -hosts does not mix, and the documentation is not up to
date
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/tools/nodetool/Repair.java#L90


>
> Is this correctly documented because I don't seem to be getting the right
> results when trying.
>
> I started up a C* 2.1.9 CCM cluster and when running
>
> * repair -h 127.0.0.1 -p 7100 repair -pr 127.0.0.2 127.0.0.3*
>
> I get the error:
>
> *nodetool: Keyspace [127.0.0.3] does not exist.*
>
> ---------------
>
> When I run it as
>
> * nodetool -h 127.0.0.1 -p 7100 repair -pr -hosts 127.0.0.2*
>
> instead it gives me the error:
> *java.lang.RuntimeException: Primary range repair should be performed on
> all nodes in the cluster.*
> *    at
> org.apache.cassandra.tools.NodeTool$Repair.execute(NodeTool.java:1873)*
> *    at
> org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:288)*
> *    at org.apache.cassandra.tools.NodeTool.main(NodeTool.java:202)*
>
> ---------------
>
> I even tried running it as
>
>
> * repair -h 127.0.0.1 -p 7100 repair -hosts 127.0.0.2 *
> and then I get
> *The current host must be part of the repair*
>
> ---------------
>
> This seems like either bug(s) or a documentation mistake?
>
> There is also a line in
> http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_repair_nodes_c.html
> which says that *You can specify which nodes have the good data for
> replacing the outdated data.* which seems to be related(and also the
> reason I tried it out)?
>
> BR
> Marcus Olsson
>

--e89a8f50355cf2bfc9051f13409c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Sep 4, 2015 at 3:50 PM, Marcus Olsson <span dir=3D"ltr">&lt;<a =
href=3D"mailto:marcus.olsson@ericsson.com" target=3D"_blank">marcus.olsson@=
ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(=
204,204,204);border-left-style:solid;padding-left:1ex">
 =20

   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    Hi,<br>
    <br>
    While checking the repair documentation at
    <a href=3D"http://docs.datastax.com/en/cassandra/2.1/cassandra/tools/to=
olsRepair.html" target=3D"_blank">http://docs.datastax.com/en/cassandra/2.1=
/cassandra/tools/toolsRepair.html</a>
    I noticed the line<b> </b><small><b>Use the </b><b><span>-hosts</span><=
/b><b> option to list the
        good nodes to use for repairing the bad nodes. Use </b><b><span>-h<=
/span></b><b> to name the bad nodes.</b></small>
    and below there was an example:<br>
    <br>
    <small><b><i>nodetool repair -pr -hosts </i></b><b><i><span>10.2</span>=
</i></b><b><i>.</i></b><b><i><span>2.20</span></i></b><b><i> </i></b><b><i>=
<span>10.2</span></i></b><b><i>.</i></b><b><i><span>2.21</span></i></b></sm=
all> which should
    do <small><b><i>A partitioner range repair of the bad partition on
          current node using the good partitions on 10.2.2.20 or
          10.2.2.21</i></b></small> according to the documentation.<br></di=
v></blockquote><div>Look like -pr and -hosts does not mix, and the document=
ation is not up to date</div><div><a href=3D"https://github.com/apache/cass=
andra/blob/trunk/src/java/org/apache/cassandra/tools/nodetool/Repair.java#L=
90">https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cass=
andra/tools/nodetool/Repair.java#L90</a><br></div><div><br></div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-styl=
e:solid;padding-left:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    Is this correctly documented because I don&#39;t seem to be getting the
    right results when trying.<br>
    <br>
    I started up a C* 2.1.9 CCM cluster and when running<small><br>
      <i><big><br>
          repair -h 127.0.0.1 -p 7100 repair -pr 127.0.0.2 127.0.0.3</big><=
/i></small><br>
    <br>
    I get the error:<br>
    <big><small><br>
      </small><b><small>nodetool: Keyspace [127.0.0.3] does not exist.</sma=
ll></b></big><br>
    <br>
    ---------------<br>
    <br>
    When I run it as<br>
    <i><br>
      nodetool -h 127.0.0.1 -p 7100 repair -pr -hosts 127.0.0.2</i><br>
    <br>
    instead it gives me the error:<br>
    <b>java.lang.RuntimeException: Primary range repair should be
      performed on all nodes in the cluster.</b><b><br>
    </b><b>=C2=A0=C2=A0=C2=A0 at
      org.apache.cassandra.tools.NodeTool$Repair.execute(NodeTool.java:1873=
)</b><b><br>
    </b><b>=C2=A0=C2=A0=C2=A0 at
      org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:288=
)</b><b><br>
    </b><b>=C2=A0=C2=A0=C2=A0 at
      org.apache.cassandra.tools.NodeTool.main(NodeTool.java:202)</b><br>
    <br>
    ---------------<br>
    <br>
    I even tried running it as<br>
    <i><br>
      repair -h 127.0.0.1 -p 7100 repair -hosts 127.0.0.2<br>
    </i><br>
    and then I get<b><br>
    </b><b>The current host must be part of the repair</b><br>
    <br>
    ---------------<br>
    <br>
    This seems like either bug(s) or a documentation mistake?<br>
    <br>
    There is also a line in
    <a href=3D"http://docs.datastax.com/en/cassandra/2.1/cassandra/operatio=
ns/ops_repair_nodes_c.html" target=3D"_blank">http://docs.datastax.com/en/c=
assandra/2.1/cassandra/operations/ops_repair_nodes_c.html</a>
    which says that <small><b>You can specify which nodes have the good
        data for replacing the outdated data.</b> <big>which seems to
        be related(and also the reason I tried it out)?</big></small><br>
    <br>
    BR<span class=3D""><font color=3D"#888888"><br>
    Marcus Olsson<br>
  </font></span></div>

</blockquote></div><br></div></div>

--e89a8f50355cf2bfc9051f13409c--