<div dir="ltr">Forwarded from our auto-evict dev:<div><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">In the case you described, if node1 and node2 had a normal replica whereas node3 had a diskless one, the replacing of the resource will turn the diskless replica into a diskful one.<br>When node1 comes back online, it will still be EVICTED. Additionally, linstor will then actually delete the previously moved DRBD-resources. However, everything else (such as storage pools, net-interfaces, etc.) is still there. The node can be restored (that is, moved out of the EVICTED status so that it can be used again) by using linstor node restore [nodename]<br></blockquote><div><br></div><div>Cheers,</div><div>Rene </div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 10, 2020 at 9:30 PM Yannis Milios <<a href="mailto:yannis.milios@gmail.com">yannis.milios@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Hello,</div><div dir="auto"><br></div><div dir="auto">Quick question, just wondering how will "auto-evict" affect a 3 node linstor cluster with a replica number of 2? Say that node1 goes down for more than an 1h, linstor will try to replace its drbd resources to either node2 or node3 assuming that the redundacy level falls below 2 and there's enough free space in the backing device on remaining nodes (will diskless clients count in this case?).</div><div dir="auto"><br></div><div dir="auto">How will linstor respond in the case where node1 comes back online? Will it just restore back drbd resources on it ? or it will just reject that node from being a part of the cluster and in this case the node will have to be rejoined to the cluster.</div><div dir="auto"><br></div><div dir="auto">Thank you,</div><div dir="auto">Yannis</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 9 Nov 2020 at 11:16, Rene Peinthor <<a href="mailto:rene.peinthor@linbit.com" target="_blank">rene.peinthor@linbit.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi!<div><br></div><div>This release brings 2 new added features, auto-evict and configurable ETCD prefixes:</div><div><br></div><div>Auto-Evict:</div><div>If a satellite has no connection to the controller for more than an hour, the controller will mark that node as EVICTED and remove all its DRBD-resources. Should this cause the total number of replicas for those resources to fall below a user-set minimum, it will then try to place new replicas on other satellites to keep enough replicas available.<br></div><div><br></div><div>ETCD-prefixes:</div><div>You can now configure the used ETCD prefix within the linstor.toml file, of course this needs to be done before the first start of the controller.</div><div>As a little drawback(cleanup) of this change, it isn't possible anymore to directly upgrade ETCD backed Linstor-Controller installation from a version prior < 1.4.3. If you have such a situation</div><div>upgrade to 1.9.0 first and then to 1.10.0.</div><div><br></div><div><div><font face="monospace" style="font-family:monospace;color:rgb(0,0,0)">linstor-server 1.10.0<br>--------------------<br> * Added auto-evict feature<br> * ETCD prefix is now configurable (migration only works now starting from version 1.4.3)<br> * Block IO can now be throttled also by iops<br> * Fixed REST-API single snapshot filtering<br> * Fixed drbd-events2 parsing race condition<br> * Fixed toggle-disk doesn't work if an unrelated node is offline<br> * Fixed race-condition in auto-tiebreaker<br> * Fixed usage of wait for snapshot-shipping<br> * REST-API version 1.5.0</font><br></div><div><br></div><div><div><font face="monospace" style="font-family:monospace;color:rgb(0,0,0)"><a href="https://www.linbit.com/downloads/linstor/linstor-server-1.10.0.tar.gz" style="font-family:monospace" target="_blank">https://www.linbit.com/downloads/linstor/linstor-server-1.10.0.tar.gz</a></font><br></div><div><br></div><div><div><div>Linstor PPA:<br><a href="https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack" rel="noreferrer" target="_blank">https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack</a></div></div><div><br></div><div>Cheers,<br></div><div>Rene</div></div></div></div></div>
_______________________________________________<br>
drbd-announce mailing list<br>
<a href="mailto:drbd-announce@lists.linbit.com" target="_blank">drbd-announce@lists.linbit.com</a><br>
<a href="https://lists.linbit.com/mailman/listinfo/drbd-announce" rel="noreferrer" target="_blank">https://lists.linbit.com/mailman/listinfo/drbd-announce</a><br>
</blockquote></div></div>-- <br><div dir="ltr">Sent from Gmail Mobile</div>
_______________________________________________<br>
Star us on GITHUB: <a href="https://github.com/LINBIT" rel="noreferrer" target="_blank">https://github.com/LINBIT</a><br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
<a href="https://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">https://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</blockquote></div>