Emmanuel Dreyfus m...@netbsd.org wrote:
Here is the problem: once readdir() has reached the end of the
directory, on Linux, telldir() will report the last entry's offset,
while on NetBSD, it will report an invalid offset (it is in fact the
offset of the next entry beyond the last one, which
Has anyone looked into whether LogCabin can provide the consistent small
storage based on RAFT for Gluster?
https://github.com/logcabin/logcabin
I have no experience with using it so I cannot say if it is good or suitable.
I do know the following project uses it and it's just not as easy to
it also has Zookeeper support etc. - just to correct this and remove the
perception that LogCabin somehow requires Zookeeper or works with it.
LogCabin as I understand is the C++ implementation of a small store based on
the Raft consensus protocol - to provide a consistent and a small
Personally, I like the third option provided that doesn't cause memory issues.
In fact, read the whole thing, transfer it to the client and let the client
handle the posix syntax.
Optionally add a path cache timeout client side that stores the directory
listing for a period of time to mitigate
On 09/14/2014 12:32 AM, Emmanuel Dreyfus wrote:
In 1lrx1si.n8tms1igmi5pm%m...@netbsd.org I explained why NetBSD
currently fails self-heald.t, but since the subjet is burried deep in a
thread, it might be worth starting a new one to talk about how to fix.
In 3 places within glusterfs code
Pranith Kumar Karampuri pkara...@redhat.com wrote:
Just to make sure I understand the problem, the issue is happening
because self-heal-daemon uses anonymous fds to perform readdirs? i.e.
there is no explicit opendir on the directory. Everytime there is a
readdir it may lead to
