Displaying 9 results from an estimated 9 matches for "decompounder".
2018 Mar 05
1
[Gluster-devel] Removal of use-compound-fops option in afr
...ent the patch at
>> https://review.gluster.org/19655
>>
>>
> If I understand it right, as of now AFR is the only component which uses
> Compound FOP. If it stops using that code, should we maintain the compound
> fop codebase at all in other places, like protocol, volgen (decompounder
> etc?)
>
Infra was also supposed to be used by gfapi when compound fops is
introduced. So I think it is not a bad idea to keep it until at least there
is a decision about it. It will be similar to loading feature modules like
quota even when quota is not used on the volume.
>
> Beca...
2017 Oct 24
2
brick is down but gluster volume status says it's fine
...rick7/digitalcorpora
> 130: option log-level WARNING
> 131: option latency-measurement off
> 132: option count-fop-hits off
> 133: subvolumes digitalcorpora-quota
> 134: end-volume
> 135:
> 136: volume /export/brick7/digitalcorpora
> 137: type performance/decompounder
> 138: option rpc-auth-allow-insecure on
> 139: option auth.addr./export/brick7/digitalcorpora.allow
> 129.174.125.204,129.174.93.204
> 140: option auth-path /export/brick7/digitalcorpora
> 141: option auth.login.b17f2513-7d9c-4174-a0c5-de4a752d46ca.password
> 6c00...
2017 Oct 24
0
brick is down but gluster volume status says it's fine
...0: option log-level WARNING
>> 131: option latency-measurement off
>> 132: option count-fop-hits off
>> 133: subvolumes digitalcorpora-quota
>> 134: end-volume
>> 135:
>> 136: volume /export/brick7/digitalcorpora
>> 137: type performance/decompounder
>> 138: option rpc-auth-allow-insecure on
>> 139: option auth.addr./export/brick7/digitalcorpora.allow
>> 129.174.125.204,129.174.93.204
>> 140: option auth-path /export/brick7/digitalcorpora
>> 141: option auth.login.b17f2513-7d9c-4174-a0c5-de4a752d46c...
2013 Nov 30
4
Full text search improvements
FTS indexing is something I hear quite often nowadays. I?ve added some hacks to make it work better for some installations, but it?s about time to think about the whole design and how it could be improved for everyone in future. Here are some of my initial thoughts.
Currently Dovecot supports 3 full text search engines: Solr, CLucene and Dovecot Squat. CLucene plugin has various features built
2017 Aug 16
0
Is transport=rdma tested with "stripe"?
...me gv0-io-stats
124: type debug/io-stats
125: option unique-id /data/brick1/gv0
126: option log-level INFO
127: option latency-measurement off
128: option count-fop-hits off
129: subvolumes gv0-quota
130: end-volume
131:
132: volume /data/brick1/gv0
133: type performance/decompounder
134: option auth.addr./data/brick1/gv0.allow *
135: option auth-path /data/brick1/gv0
136: option auth.login.2d6e8c76-47ed-4ac4-87ff-f96693f048b5.password e5fe5e7e-6722-4845-8149-edaf14065ac0
137: option auth.login./data/brick1/gv0.allow 2d6e8c76-47ed-4ac4-87ff-f96693f048b5
138:...
2017 Aug 15
2
Is transport=rdma tested with "stripe"?
On Tue, Aug 15, 2017 at 01:04:11PM +0000, Hatazaki, Takao wrote:
> Ji-Hyeon,
>
> You're saying that "stripe=2 transport=rdma" should work. Ok, that
> was firstly I wanted to know. I'll put together logs later this week.
Note that "stripe" is not tested much and practically unmaintained. We
do not advise you to use it. If you have large files that you
2017 Aug 18
1
Is transport=rdma tested with "stripe"?
...> 125: option unique-id /data/brick1/gv0
> 126: option log-level INFO
> 127: option latency-measurement off
> 128: option count-fop-hits off
> 129: subvolumes gv0-quota
> 130: end-volume
> 131:
> 132: volume /data/brick1/gv0
> 133: type performance/decompounder
> 134: option auth.addr./data/brick1/gv0.allow *
> 135: option auth-path /data/brick1/gv0
> 136: option auth.login.2d6e8c76-47ed-4ac4-87ff-f96693f048b5.password e5fe5e7e-6722-4845-8149-edaf14065ac0
> 137: option auth.login./data/brick1/gv0.allow 2d6e8c76-47ed-4ac4-87ff-f...
2018 Jan 12
0
Creating cluster replica on 2 nodes 2 bricks each.
---------- Forwarded message ----------
From: Jose Sanchez <josesanc at carc.unm.edu>
Date: 11 January 2018 at 22:05
Subject: Re: [Gluster-users] Creating cluster replica on 2 nodes 2 bricks
each.
To: Nithya Balachandran <nbalacha at redhat.com>
Cc: gluster-users <gluster-users at gluster.org>
Hi Nithya
Thanks for helping me with this, I understand now , but I have few
2018 Jan 11
3
Creating cluster replica on 2 nodes 2 bricks each.
Hi Nithya
Thanks for helping me with this, I understand now , but I have few questions.
When i had it setup in replica (just 2 nodes with 2 bricks) and tried to added , it failed.
> [root at gluster01 ~]# gluster volume add-brick scratch replica 2 gluster01ib:/gdata/brick2/scratch gluster02ib:/gdata/brick2/scratch
> volume add-brick: failed: /gdata/brick2/scratch is already part of a