<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Am 02.12.13 15:47, schrieb Gregory Holt:<br>
<span style="white-space: pre;">> Achieving this transparently is
part of the ongoing plans, starting<br>
> with things like the DiskFile refactoring and SSync. The idea
is to<br>
> isolate the direct disk access from other servers/tools,
something<br>
> that (for instance) RSync has today. Once the isolation is
there, it<br>
> should be fairly straightforward to have incoming requests
for a<br>
> ring^20 partition look on the local disk in a directory
structure<br>
> that was originally created for a ring^19 partition, or even
vice<br>
> versa. Then, there will be no need to move data around just
for a<br>
> ring-doubling or halving, and no down time to do so.<br>
</span><br>
That sounds great! Is someone already working on this (I know about
the ongoing DiskFile refactoring) or even a blueprint available? I
was aware of the idea about multiple rings on the same policy but
not about support for rings with a modified partition power. <br>
<span style="white-space: pre;"><br>
> That said, if you want create a tool that allows such ring
shifting<br>
> in the interim, it should work with smaller clusters that
don't mind<br>
> downtime. I would prefer that it not become a core tool
checked<br>
> directly into swift/python-swiftclient, just because of the
plans<br>
> stated above that should one day make it obsolete.<br>
</span><br>
Yes, that makes a lot of sense. In fact the tool is already working;
I think the best way is to enhance the docs and to list it as a
related Swift project once I'm done with this. <br>
<br>
Christian<br>
<br>
<br>
<br>
</body>
</html>