Displaying 5 results from an estimated 5 matches for "iot_schedul".
Did you mean:
iot_schedule
2018 Jan 25
2
parallel-readdir is not recognized in GlusterFS 3.12.4
...e-f47c04297aaa.
sources=[0] sinks=1
I enabled debug logging for that volume's client mount with `gluster volume
set homes diagnostics.client-log-level DEBUG` and then I saw this in the
client mount log the next time it disconnected:
[2018-01-24 08:55:19.138810] D [MSGID: 0] [io-threads.c:358:iot_schedule]
0-homes-io-threads: LOOKUP scheduled as fast fop
[2018-01-24 08:55:19.138849] D [MSGID: 0] [dht-common.c:2711:dht_lookup]
0-homes-dht: Calling fresh lookup for
/vchebii/revtrans/Hircus-XM_018067032.1.pep.align.fas on
homes-readdir-ahead-1
[2018-01-24 08:55:19.138928] D [MSGID: 0] [io-threads.c:35...
2018 Jan 26
0
parallel-readdir is not recognized in GlusterFS 3.12.4
...sinks=1
>
> I enabled debug logging for that volume's client mount with `gluster volume
> set homes diagnostics.client-log-level DEBUG` and then I saw this in the
> client mount log the next time it disconnected:
>
> [2018-01-24 08:55:19.138810] D [MSGID: 0] [io-threads.c:358:iot_schedule]
> 0-homes-io-threads: LOOKUP scheduled as fast fop
> [2018-01-24 08:55:19.138849] D [MSGID: 0] [dht-common.c:2711:dht_lookup]
> 0-homes-dht: Calling fresh lookup for
> /vchebii/revtrans/Hircus-XM_018067032.1.pep.align.fas on
> homes-readdir-ahead-1
> [2018-01-24 08:55:19.138928]...
2018 Jan 26
1
parallel-readdir is not recognized in GlusterFS 3.12.4
...led debug logging for that volume's client mount with `gluster
> volume
> > set homes diagnostics.client-log-level DEBUG` and then I saw this in the
> > client mount log the next time it disconnected:
> >
> > [2018-01-24 08:55:19.138810] D [MSGID: 0] [io-threads.c:358:iot_schedule]
> > 0-homes-io-threads: LOOKUP scheduled as fast fop
> > [2018-01-24 08:55:19.138849] D [MSGID: 0] [dht-common.c:2711:dht_lookup]
> > 0-homes-dht: Calling fresh lookup for
> > /vchebii/revtrans/Hircus-XM_018067032.1.pep.align.fas on
> > homes-readdir-ahead-1
> >...
2018 Jan 24
0
parallel-readdir is not recognized in GlusterFS 3.12.4
Adding Poornima to take a look at it and comment.
On Tue, Jan 23, 2018 at 10:39 PM, Alan Orth <alan.orth at gmail.com> wrote:
> Hello,
>
> I saw that parallel-readdir was an experimental feature in GlusterFS
> version 3.10.0, became stable in version 3.11.0, and is now recommended for
> small file workloads in the Red Hat Gluster Storage Server
> documentation[2].
2018 Jan 23
6
parallel-readdir is not recognized in GlusterFS 3.12.4
Hello,
I saw that parallel-readdir was an experimental feature in GlusterFS
version 3.10.0, became stable in version 3.11.0, and is now recommended for
small file workloads in the Red Hat Gluster Storage Server
documentation[2]. I've successfully enabled this on one of my volumes but I
notice the following in the client mount log:
[2018-01-23 10:24:24.048055] W [MSGID: 101174]