Il 2020-03-22 06:55 Amar Tumballi ha scritto:
When 'Sharding' is enabled, a single file gets broken into multiple files, based on offset. But when one does 'readdir()' (ie, ls), those files are hidden, and only the valid entry is shown from the Shard xlator in the graph.
Sure.
Now, when shard is disabled, these files are exposed directly on the mountpoint, confusing the user, and making the previously successfully written files inaccessible.
Ok, I was missing this piece - that single shards become themselves visible. This will crearly wreak havoc on user application.
In such cases, would re-enabling sharding fix the problem?
Hope this helps you to understand why disabling Shard once enabled is hard!
Thanks, it was very helpful. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it [1] email: g.danti@xxxxxxxxxx - info@xxxxxxxxxx GPG public key ID: FF5F32A8 ________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
