[Gluster-devel] Questions about BDB storage translator

[Anand Babu Periasamy]

We ideally want to separate out wild card matching into a separate
switch-case translator. That way every translator gets this feature
and our design still remains elegant.

Current switch-case will be re-written with a new design.

--
Anand Babu Periasamy
GPG Key ID: 0x62E15A31
Blog [http://ab.freeshell.org]
The GNU Operating System [http://www.gnu.org]
Z RESEARCH Inc [http://www.zresearch.com]



Anand Avati wrote:
>> 1) It's been stated that it doesn't support hard links and is not POSIX
>> compliant due to fops not being supported.  Are these limitations in the
>> current version, or are there implementation details that make adding these
>> features not feasible (at least at this time)?
> 
> 
> The current implementation has limitations to support hardlinks. We might
> support it in the future. We are still not sure whether or not we will bring
> in support for per-file attributes/ownership. BDB translator is meant to
> store 'lot of small files' typically for serving off the web and other
> special uses where ownership/permission is not of high concern.
> 
> 
> 2) Is there any interest in making the BDB translator more similar to the
>> stripe translator in that it will only kick in if files match certain
>> criteria, such as below 100k?  Ideally, the switch translator would be able
>> to handle this, but in any case it would be nice to have a share that
>> striped files over X MB and used BDB for files under Y KB (but more so if
>> the BDB storage system was more POSIX compliant).
> 
> 
> We plan to bring in a directory match option (with wildcards) for turning
> on/off bdb on those volumes. This can be driven or changed by user feedback.
> 
> 
> avati
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/gluster-devel