Attila Bukor has posted comments on this change. ( 
http://gerrit.cloudera.org:8080/11218 )

Change subject: KUDU-2538: [docs] Document how to manually recover from Cfile 
corruption
......................................................................


Patch Set 3:

(5 comments)

http://gerrit.cloudera.org:8080/#/c/11218/3/docs/troubleshooting.adoc
File docs/troubleshooting.adoc:

http://gerrit.cloudera.org:8080/#/c/11218/3/docs/troubleshooting.adoc@640
PS3, Line 640: Until 
link:https://issues.apache.org/jira/browse/KUDU-2469[KUDU-2469] is
Do we want to go into so many details as to list JIRAs?

If yes, maybe a note at the bottom explaining that this could happen due to 
disk issues but there are improvements planned that would reduce the chances of 
this happening, and list the JIRAs there.


http://gerrit.cloudera.org:8080/#/c/11218/3/docs/troubleshooting.adoc@645
PS3, Line 645: 
link:https://kudu.apache.org/docs/command_line_tools_reference.html#cluster-ksck[ksck
 tool].
These links should be relative:

link:command_line_tools_reference.html#custer-ksck[ksck tool]


http://gerrit.cloudera.org:8080/#/c/11218/3/docs/troubleshooting.adoc@655
PS3, Line 655: 
`link:https://kudu.apache.org/docs/command_line_tools_reference.html#remote_replica-delete[remote_replica
 delete tool]`.
Same here + the backticks should wrap only `remote_replica delete`:

link:command_line_tools_reference.html#remote_replica-delete[`remote_replica 
delete` tool].


http://gerrit.cloudera.org:8080/#/c/11218/3/docs/troubleshooting.adoc@668
PS3, Line 668: 
`link:https://kudu.apache.org/docs/command_line_tools_reference.html#tablet-unsafe_replace_tablet[unsafe_replace_tablet
 tool]`.
Same here


http://gerrit.cloudera.org:8080/#/c/11218/3/docs/troubleshooting.adoc@671
PS3, Line 671: sudo -u kudu kudu tablet unsafe_replace_tablet 
<master_addresses> <tablet_id>
As this tool will only be available in 1.8.0 and above, maybe we should put a 
note about it and suggest upgrading in case the users run into this corruption 
on an older release with the only workaround being deleting the whole range 
partition (or table in case there's no range partitioning).

Alternatively, we could also describe how to remove the affected rowset 
manually from the tablet metadata, but if we do that, we should add a huge 
warning about it being unsafe.



--
To view, visit http://gerrit.cloudera.org:8080/11218
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: Ieefd472bef104921de7cab442fd49ab32c0fe81b
Gerrit-Change-Number: 11218
Gerrit-PatchSet: 3
Gerrit-Owner: Grant Henke <[email protected]>
Gerrit-Reviewer: Andrew Wong <[email protected]>
Gerrit-Reviewer: Attila Bukor <[email protected]>
Gerrit-Reviewer: Grant Henke <[email protected]>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Will Berkeley <[email protected]>
Gerrit-Comment-Date: Wed, 15 Aug 2018 10:00:52 +0000
Gerrit-HasComments: Yes

Reply via email to