# Is there anything bad when executes nodetool repair whose host ip doesn't match token range?

**URL:** <https://forum.scylladb.com/t/is-there-anything-bad-when-executes-nodetool-repair-whose-host-ip-doesnt-match-token-range/2019>\
**Category:** ScyllaDB\
**Tags:** repair, nodetool\
**Created:** [May 15, 2024, 1:54am UTC](https://forum.scylladb.com/t/is-there-anything-bad-when-executes-nodetool-repair-whose-host-ip-doesnt-match-token-range/2019 "2024-05-15T01:54:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![qiuqiu](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/qiuqiu/32/1534_2.png) [@qiuqiu](https://forum.scylladb.com/u/qiuqiu)\
**Post date:** [May 15, 2024, 1:54am UTC](https://forum.scylladb.com/t/is-there-anything-bad-when-executes-nodetool-repair-whose-host-ip-doesnt-match-token-range/2019/1 "2024-05-15T01:54:08Z")

</div>

In order to make it specific enough, here set an example, a cluster with nodes `127.0.0.1, 127.0.0.2, 127.0.0.3` , and consistency level is quorum. Here is the process: firstly, get the token range by executing `nodetool describering <keyspace>`, then get:

```auto
TokenRange(start_token:9140250233623497227, end_token:9153470637258054361, endpoints:[127.0.0.1, 127.0.0.2]...

```

Secondly, execute

```auto
nodetool -h 127.0.0.3 repair -pr -st 9140250233623497227 -et 9153470637258054361 

```

Finally, logs print repair successfully.

Is there anything bad when executes nodetool repair whose host ip doesn’t match token range?

---

<div class="post-metadata">

**Author:** ![avikivity](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/avikivity/32/38_2.png) [@avikivity](https://forum.scylladb.com/u/avikivity)\
**Post date:** [July 9, 2024, 1:09pm UTC](https://forum.scylladb.com/t/is-there-anything-bad-when-executes-nodetool-repair-whose-host-ip-doesnt-match-token-range/2019/2 "2024-07-09T13:09:16Z")

</div>

I don’t think there’s any problem.