Alexey Serbin has posted comments on this change.

Change subject: [docs] Add admin workflow for recovering from disk failure
......................................................................


Patch Set 1:

(2 comments)

http://gerrit.cloudera.org:8080/#/c/6606/1/docs/administration.adoc
File docs/administration.adoc:

Line 605: 
Since replacing failed disk would usually require restarting the machine (if 
not hot-pluggable), would it make sense to add  a note to disable the 
kudu-tserver when working on bringing on the new device and clearing the 
directory structure?

Something like

chkconfig kudu-tserver off

for the case of RPM-based Linux distro.


PS1, Line 608: /data/0/kudu-tserver-wal /data/1/kudu-tserver 
/data/2/kudu-tserver
Is it necessary to create empty directories once the original/corrupted were 
removed?


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

Gerrit-MessageType: comment
Gerrit-Change-Id: I6541bffc5e9546c523df610fd8c025dd05e403bf
Gerrit-PatchSet: 1
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Dan Burkert <[email protected]>
Gerrit-Reviewer: Adar Dembo <[email protected]>
Gerrit-Reviewer: Alexey Serbin <[email protected]>
Gerrit-Reviewer: Ambreen Kazi <[email protected]>
Gerrit-Reviewer: Andrew Wong <[email protected]>
Gerrit-Reviewer: Andrew Wong <[email protected]>
Gerrit-Reviewer: Dan Burkert <[email protected]>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Todd Lipcon <[email protected]>
Gerrit-HasComments: Yes

Reply via email to