Hi Shyam,
I've been discussing this stuff with Krishnan and we ended up with a
proposal (see attached file).
There many comments to explain how it works.
What do you think about this proposal ?
Xavi
On 11/11/2014 07:42 PM, Shyam wrote:
On 11/10/2014 09:59 AM, Xavier Hernandez wrote:
Hi
Came across this RDMA focused blog while looking for some
stuff (am setting up home Infiniband network again):
http://rdmamojo.com
It's the personal blog of one of the Mellanox guys,
and has all kinds of useful info on RDMA programming,
OS setup for Infiniband cards, and similar.
+ Justin
[Adding gluster-users]
On 10/29/2014 12:11 PM, Raghavendra Bhat wrote:
On Monday 27 October 2014 06:34 PM, Vijay Bellur wrote:
Hi All,
As we move closer to the release of 3.6.0, we are looking to add a
release maintainer for the 3.6.0 development branch (release-3.6).
Primary requirements for
Past couple of days have been slow for me and I'm new to the FOP stuff
so I will try and finish something available soon with potentially
some benchmarks. Will try and post the feature page and make some of
the code available.
The API can always be expanded to have atomic stream writes - it's
Out of general interest - How much data and what kind are you looking to store?
How does this relate to RAFT as in consensus for cluster? Some form of
leader selection and then leader propagates/makes available all the
SQLite data or storing counters for consensus itself?
On Tue, Nov 11, 2014
On 11/11/2014 05:25 PM, Kiran Patil wrote:
I have installed gluster v3.6.1 from
http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-6/
The /tests/bugs/bug-1112559.t testcase passed in all 3 runs and rest
of the two tests quota-anon-fd-nfs.t,
On Wed, 12 Nov 2014 07:17:25 -0500 (EST)
Krishnan Parthasarathi kpart...@redhat.com wrote:
All,
We have come across behaviours and features of GlusterFS that are left
unexplained for various reasons. Thanks to Justin Clift for
encouraging me to come up with a document that tries to fill
Hi all,
At the moment, our smoke tests in Jenkins only run on a
replicated volume. Extending that out to other volume types
should (in theory :) help catch other simple gotchas.
Xavi has put together a patch for doing just this, which I'd
like to apply and get us running:
\ At the moment, our smoke tests in Jenkins only run on a
replicated volume. Extending that out to other volume types
should (in theory :) help catch other simple gotchas.
Xavi has put together a patch for doing just this, which I'd
like to apply and get us running:
Hi guys,
I've got a geo-rep setup which copies data across 3 DCs, it works fine,
but I've just spotted that the both the master and slave server ( the
main ones ) ran out of inodes.
Looking through the directories which have lots of files, the
On 11/12/2014 06:13 PM, Pranith Kumar Karampuri wrote:
On 11/11/2014 05:25 PM, Kiran Patil wrote:
I have installed gluster v3.6.1
from
http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-6/
The /tests/bugs/bug-1112559.t testcase passed in all 3 runs and rest
of the
+1, excellent idea, this will definitely give an additional comfort zone
for learning glusterfs faster.
On 11/12/2014 05:47 PM, Krishnan Parthasarathi wrote:
All,
We have come across behaviours and features of GlusterFS that are left
unexplained for various reasons. Thanks to Justin Clift
It's safe to purge everything under .processed. That what geo-rep had
already replicated, so it's OK to delete it.
Also, consider purging these entries periodically as geo-rep doesn't purge
them on it's own (at least for now).
Venky
On Thu, Nov 13, 2014 at 3:27 AM, Andrea Tartaglia
On 11/13/2014 03:23 AM, Justin Clift wrote:
Hi all,
At the moment, our smoke tests in Jenkins only run on a
replicated volume. Extending that out to other volume types
should (in theory :) help catch other simple gotchas.
Xavi has put together a patch for doing just this, which I'd
like to
14 matches
Mail list logo
