On 2/3/2018 8:58 AM, Dan Ragle wrote:
On 2/2/2018 2:13 AM, Nithya Balachandran wrote:
Hi Dan,
It sounds like you might be running into [1]. The patch has been
posted upstream and the fix should be in the next release.
In the meantime, I'm afraid there is no way to get around this without
,
Nithya
[1]https://bugzilla.redhat.com/show_bug.cgi?id=1541264
Much appreciated. Will watch for the next release and retest then.
Cheers!
Dan
On 2 February 2018 at 02:57, Dan Ragle <dan...@biblestuph.com
<mailto:dan...@biblestuph.com>> wrote:
On 1/30/2018 6:31 AM, Raghaven
On 1/30/2018 6:31 AM, Raghavendra Gowdappa wrote:
- Original Message -
From: "Dan Ragle" <dan...@biblestuph.com>
To: "Raghavendra Gowdappa" <rgowd...@redhat.com>, "Ravishankar N"
<ravishan...@redhat.com>
Cc: gluster-users@gluster.org
On 1/26/2018 11:53 PM, Ravishankar N wrote:
On 01/27/2018 02:29 AM, Dan Ragle wrote:
On 1/25/2018 8:21 PM, Ravishankar N wrote:
On 01/25/2018 11:04 PM, Dan Ragle wrote:
*sigh* trying again to correct formatting ... apologize for the
earlier mess.
Having a memory issue with Gluster
On 1/29/2018 2:36 AM, Raghavendra Gowdappa wrote:
- Original Message -
From: "Ravishankar N" <ravishan...@redhat.com>
To: "Dan Ragle" <dan...@biblestuph.com>, gluster-users@gluster.org
Cc: "Csaba Henk" <ch...@redhat.com>, "Nie
you the dumps now. Will
update soon.
Does your data set include a lot of directories?
The volume in question has 1M+ files and 77k+ directories.
Cheers!
Dan
Thanks,
Nithya
On 27 January 2018 at 10:23, Ravishankar N <ravishan...@redhat.com> wrote:
On 01/27/2018 02:29 AM, Dan
On 1/25/2018 8:21 PM, Ravishankar N wrote:
On 01/25/2018 11:04 PM, Dan Ragle wrote:
*sigh* trying again to correct formatting ... apologize for the earlier mess.
Having a memory issue with Gluster 3.12.4 and not sure how to troubleshoot. I
don't *think* this is expected behavior
killer.
Is there potentially something misconfigured here?
I did see a reference to a memory leak in another thread in this list, but that had to do with the setting of quotas, I don't have
any quotas set on my system.
Thanks,
Dan Ragle
dan...@biblestuph.com
On 1/25/2018 11:04 AM, Dan Ragle
.
Restart the test script and the memory begins slowly growing again. This
is obviously a contrived app environment. With my intended application
load it takes about a week or so for the memory to get high enough to
invoke the oom killer. Is there potentially something misconfigured
here? Thanks, Dan
In setting up my v3.10.1 cluster I found that using the newer
cache-invalidation features seemed to help performance in at least some
ways; but I haven't seen a lot of discussion about them following the
initial introduction.
features.cache-invalidation: on
10 matches
Mail list logo
