Skip to content

riak admin node repair tests - #29

Merged
martinsumner merged 10 commits into
OpenRiak:openriak-3.4from
TI-Tokyo:tiot/openriak-3.4/node-repair-cli
Jun 29, 2026
Merged

riak admin node repair tests#29
martinsumner merged 10 commits into
OpenRiak:openriak-3.4from
TI-Tokyo:tiot/openriak-3.4/node-repair-cli

Conversation

@hmmr

@hmmr hmmr commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

@hmmr hmmr changed the title basic_command_line: add riak admin node repair test riak admin node repair tests Jun 23, 2026
@hmmr
hmmr force-pushed the tiot/openriak-3.4/node-repair-cli branch from a62e080 to 290d821 Compare June 24, 2026 11:30
@martinsumner

martinsumner commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

The node_repair_cli test appears to be stuck when I run it locally:

2026-06-26 11:37:21.225164+01:00 [info] * checking that resumed repairs match the pre-stop state
2026-06-26 11:37:21.225504+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
2026-06-26 11:37:23.588440+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
...
2026-06-26 11:45:08.617933+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
2026-06-26 11:45:11.037857+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
2026-06-26 11:45:13.444869+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
2026-06-26 11:45:15.852732+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
2026-06-26 11:45:18.259931+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
2026-06-26 11:45:20.691815+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
2026-06-26 11:45:23.087613+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
2026-06-26 11:45:25.470859+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
...

If I run the node status command I get:

~/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
Node repairs on dev1@127.0.0.1
+-------------+-------------------------------------------------+----------+
|     mod     |                       idx                       |   pid    |
+-------------+-------------------------------------------------+----------+
|riak_kv_vnode|730750818665451459101842416358141509827966271488 |<0.1739.0>|
|riak_kv_vnode|1255977969581244695331291653115555720016817029120|<0.2098.0>|
|riak_kv_vnode|251195593916248939066258330623111144003363405824 |<0.1121.0>|
|riak_kv_vnode|981946412581700398168100746981252653831329677312 |<0.1798.0>|
|riak_kv_vnode|1096126227998177188652763624537212264741949407232|<0.2057.0>|
|riak_kv_vnode|433883298582611803841718934712646521460354973696 |<0.1449.0>|
|riak_kv_vnode|365375409332725729550921208179070754913983135744 |<0.1433.0>|
|riak_kv_vnode|616571003248974668617179538802181898917346541568 |<0.1455.0>|
|riak_kv_vnode|1438665674247607560106752257205091097473808596992|<0.2175.0>|
|riak_kv_vnode|799258707915337533392640142891717276374338109440 |<0.1768.0>|
|riak_kv_vnode|456719261665907161938651510223838443642478919680 |<0.1450.0>|
|riak_kv_vnode|639406966332270026714112114313373821099470487552 |<0.1465.0>|
|riak_kv_vnode|525227150915793236229449236757414210188850757632 |<0.1460.0>|
|riak_kv_vnode|1278813932664540053428224228626747642198940975104|<0.2128.0>|
|riak_kv_vnode|1004782375664995756265033322492444576013453623296|<0.1807.0>|
|riak_kv_vnode|890602560248518965780370444936484965102833893376 |<0.1782.0>|
|riak_kv_vnode|1164634117248063262943561351070788031288321245184|<0.2104.0>|
|riak_kv_vnode|1073290264914881830555831049026020342559825461248|<0.1836.0>|
|riak_kv_vnode|1370157784997721485815954530671515330927436759040|<0.2142.0>|
|riak_kv_vnode|342539446249430371453988632667878832731859189760 |<0.1122.0>|
|riak_kv_vnode|1347321821914426127719021955160323408745312813056|<0.2141.0>|
|riak_kv_vnode|822094670998632891489572718402909198556462055424 |<0.1754.0>|
|riak_kv_vnode|707914855582156101004909840846949587645842325504 |<0.1494.0>|
|riak_kv_vnode|1187470080331358621040493926581979953470445191168|<0.2095.0>|
|riak_kv_vnode|913438523331814323877303020447676887284957839360 |<0.1785.0>|
|riak_kv_vnode|548063113999088594326381812268606132370974703616 |<0.1458.0>|
+-------------+-------------------------------------------------+----------+

Node repairs on dev2@127.0.0.1
+-------------+-------------------------------------------------+--------------+
|     mod     |                       idx                       |     pid      |
+-------------+-------------------------------------------------+--------------+
|riak_kv_vnode|1255977969581244695331291653115555720016817029120|<24560.6602.0>|
+-------------+-------------------------------------------------+--------------+

ok
martinsumner@Martins-Laptop riak % ~/rt/riak/current/dev/dev1/riak/bin/riak admin transfers                
No transfers active

Active Transfers:


ok

[EDIT]

It eventually passed though:

2026-06-26 11:49:14.603096+01:00 [info] Running: /Users/martinsumner/rt/riak/current/dev/dev1/riak/bin/riak admin node repair status -n all
2026-06-26 11:49:15.004797+01:00 [notice] node_repair_cli_test Test Run Complete pass
2026-06-26 11:49:15.012594+01:00 [info] Stopping cover
2026-06-26 11:49:15.012673+01:00 [info] Success

Should it have taken that long?

@martinsumner
martinsumner merged commit c99e342 into OpenRiak:openriak-3.4 Jun 29, 2026
2 checks passed
@hmmr
hmmr deleted the tiot/openriak-3.4/node-repair-cli branch June 29, 2026 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants