So sharding in its current form should still work fine in the non-VM-store
use-cases
as long as they are single-writer-to-large-file workloads.
I am starting (actually resuming :)) work on making it useful for
multiple-writers workload.
Sharding will need to use locks to synchronize modification
On Sat, Aug 6, 2016 at 7:37 AM, Niels de Vos wrote:
> Hi,
>
> As *we* all are aware, striped volumes should not be used anymore. The
> replacement for this is sharding, available and stable since the latest
> 3.7 releases and 3.8. Unfortunately users still create striped
On Sat, Aug 6, 2016 at 4:37 AM, Niels de Vos wrote:
> Hi,
>
> As *we* all are aware, striped volumes should not be used anymore. The
> replacement for this is sharding, available and stable since the latest
> 3.7 releases and 3.8. Unfortunately users still create striped
Hi,
As *we* all are aware, striped volumes should not be used anymore. The
replacement for this is sharding, available and stable since the latest
3.7 releases and 3.8. Unfortunately users still create striped volumes,
and some even write blog posts with examples.
We should actively recommend