<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>What happens if one of the nodes in the cluster is not recoverable at all. IE fried motherboard, can you just start up the vm's that were on the dead machine on another machine in the cluster?<br></div><div><br></div><div><br></div><div>I do love the fact that there is not a start up order constraint any more. <br></div><div><br></div><div>I also agree that yo should be able to re balance the cluster in the feature, the cluster should easily be willing to accept change. <br></div><div><br></div><div>---<br></div><div>Message: 1<br>Date: Mon, 26 Sep 2011 00:01:02 +0900<br>From: MORITA Kazutaka <<a href="mailto:morita.kazutaka@lab.ntt.co.jp">morita.kazutaka@lab.ntt.co.jp</a>><br>To: Liu Yuan <<a href="mailto:namei.unix@gmail.com">namei.unix@gmail.com</a>><br>Cc: <a
href="mailto:sheepdog@lists.wpkg.org">sheepdog@lists.wpkg.org</a><br>Subject: Re: [Sheepdog] [PATCH v2] sheep: tame sheep to recover the<br> crash cluster<br>Message-ID: <87d3eoll8x.wl%<a href="mailto:morita.kazutaka@lab.ntt.co.jp">morita.kazutaka@lab.ntt.co.jp</a>><br>Content-Type: text/plain; charset=US-ASCII<br><br>At Sun, 25 Sep 2011 12:00:20 +0800,<br>Liu Yuan wrote:<br>> <br>> From: Liu Yuan <<a href="mailto:tailai.ly@taobao.com">tailai.ly@taobao.com</a>><br>> <br>> Hi Kazum,<br>>
would this solve the data loss problem as you mentioned when
there is no epoch overlap? This patch would allow cluster to recover as
if the master (last failed node) were no ever crashed.<br><br>The concept of mastership transfer is great! I think this is the<br>right way to go.<br><br>But your patch has some problems. Here is a test case to reproduce<br>the problems:<br><br> #!/bin/bash<br> <br> # create a directory which has a different creation time<br> sheep /store/1 -p 7001<br> sleep 1<br> collie cluster format -p 7001<br> collie cluster shutdown -p 7001<br> sleep 1<br> <br> # start Sheepdog<br> sheep /store/0 -p 7000<br> sleep 1<br> collie cluster format -p 7000<br> <br> while true; do<br> sheep /store/1 -p 7001<br> sheep /store/2 -p 7002<br> <br> # wait for node join<br>
while [ "`collie cluster info -p 7002 -r 2>&1 | head -1`" != 'running' ]; do<br> sleep 0.1<br> done<br> <br> if [ "`collie node list -p 7002 -r | wc -l`" -ne 2 ]; then<br> # break if the result is not correct<br> break<br> fi<br> <br> pkill -f "sheep /store/2"<br> done<br> <br> # show results<br> collie cluster info -p 7000<br> collie cluster info -p 7002<br><br><br>The detailed reasons are below.<br><br>> @@ -975,17 +992,6 @@ static void __sd_deliver(struct cpg_event *cevent)<br>> addr_to_str(name, sizeof(name), m->from.addr, m->from.port),<br>>
m->pid);<br>> <br>> - /*<br>> - * we don't want to perform any deliver events until we<br>> - * join; we wait for our JOIN message.<br>> - */<br>> - if (!sys->join_finished) {<br>> - if (m->pid != sys->this_pid || m->nodeid != sys->this_nodeid) {<br>> - cevent->skip = 1;<br>> - return;<br>> - }<br>> - }<br>> -<br><br>Sheepdog assumes that only joined nodes handle the delived messages,<br>so we cannot remove this block. You should pass only mastership<br>transfer events here.<br><br><br>> if (m->op == SD_MSG_JOIN)
{<br>> uint32_t nodeid = m->nodeid;<br>> uint32_t pid = m->pid;<br>> @@ -1052,7 +1058,15 @@ static void send_join_response(struct work_deliver *w)<br>> jm->nr_leave_nodes++;<br>> }<br>> print_node_list(&sys->leave_list);<br>> + } else if (jm->result != SD_RES_SUCCESS &&<br>> + jm->epoch > sys->epoch &&<br>> + jm->cluster_status == SD_STATUS_WAIT_FOR_JOIN) {<br>> + eprintf("Transfer mastership.\n");<br>> + leave_cluster();<br>>
+ eprintf("Restart me later when master is up, please.Bye.\n");<br>> + exit(1);<br>> }<br>> + jm->epoch = sys->epoch;<br>> send_message(sys->handle, m);<br>> }<br>> <br>> @@ -1090,15 +1104,23 @@ static void __sd_deliver_done(struct cpg_event *cevent)<br>> lm = (struct leave_message *)m;<br>> add_node_to_leave_list(m);<br>> <br>> - if (lm->epoch > sys->leave_epoch)<br>> - sys->leave_epoch = lm->epoch;<br>>
+ /* Sheep needs this to identify itself as master.<br>> + * Now mastership transfer is done.<br>> + */<br>> + if (!sys->join_finished) {<br>> + sys->join_finished = 1;<br>> + move_node_to_sd_list(sys->this_nodeid, sys->this_pid, sys->this_node);<br>> + sys->epoch = get_latest_epoch();<br>> +
}<br><br>IIUC, this codes assume that all other nodes will send leave messages<br>because this node has a newer epoch, so this can be a master. But the<br>assumption is wrong because the node which has a completely wrong<br>epoch information (e.g. a node with a different creation time) also<br>sends a leave message.<br><br>My suggestion is introducing another message type something like<br>SD_MSG_MASTER_TRANSFER. I think we should clearly distinguish master<br>transfer events from leave messages.<br><br><br>Thanks,<br><br>Kazutaka<br><br><br>> <br>> nr_local = get_nodes_nr_epoch(sys->epoch);<br>> nr = get_nodes_nr_from(&sys->sd_node_list);<br>>
nr_leave = get_nodes_nr_from(&sys->leave_list);<br>> +<br>> + dprintf("%d == %d + %d \n", nr_local, nr, nr_leave);<br>> if (nr_local == nr + nr_leave) {<br>> sys->status = SD_STATUS_OK;<br>> - sys->epoch = sys->leave_epoch + 1;<br>> + sys->epoch = sys->epoch;<br>> update_epoch_log(sys->epoch);<br>>
update_epoch_store(sys->epoch);<br>> }<br>> @@ -1931,7 +1953,6 @@ join_retry:<br>> sys->handle = cpg_handle;<br>> sys->this_nodeid = nodeid;<br>> sys->this_pid = getpid();<br>> - sys->leave_epoch = 0;<br>> <br>> ret = set_addr(nodeid, port);<br>> if (ret)<br>> diff --git a/sheep/sheep_priv.h b/sheep/sheep_priv.h<br>> index 6680f79..4711cdd 100644<br>> --- a/sheep/sheep_priv.h<br>> +++ b/sheep/sheep_priv.h<br>> @@ -144,7 +144,6 @@ struct cluster_info {<br>> int nr_outstanding_reqs;<br>> <br>> uint32_t recovered_epoch;<br>> -
uint32_t leave_epoch; /* The highest number in the clsuter */<br>> <br>> int use_directio;<br>> <br>> -- <br>> 1.7.6.1<br>> <br>> -- <br>> sheepdog mailing list<br>> <a href="mailto:sheepdog@lists.wpkg.org">sheepdog@lists.wpkg.org</a><br>> <a href="http://lists.wpkg.org/mailman/listinfo/sheepdog" target="_blank">http://lists.wpkg.org/mailman/listinfo/sheepdog</a><br><br></div></div></body></html>