[Gluster-users] Transport endpoint is not connected failures in

[brandon at thinkhuge.net]

Hello Nithya,

 

I removed several options that I admit I didn't quite understand and I had added from Google searches.  Was dumb for me to have added in the first place not understanding them.

 

1 of these options apparently was causing directory listing to be about 7 seconds vs when I cut down to more minimal volume settings 1-2 seconds.   That is with about 14,000 files in the largest directory.

 

Before:

 

Options Reconfigured:

transport.address-family: inet

nfs.disable: on

cluster.min-free-disk: 1%

performance.cache-size: 8GB

performance.cache-max-file-size: 128MB

diagnostics.brick-log-level: WARNING

diagnostics.brick-sys-log-level: WARNING

client.event-threads: 3

performance.client-io-threads: on

performance.io-thread-count: 24

network.inode-lru-limit: 1048576

performance.parallel-readdir: on

performance.cache-invalidation: on

performance.md-cache-timeout: 600

features.cache-invalidation: on

features.cache-invalidation-timeout: 600

 

After:

 

Options Reconfigured:

performance.io-thread-count: 32

performance.client-io-threads: on

client.event-threads: 8

diagnostics.brick-sys-log-level: WARNING

diagnostics.brick-log-level: WARNING

performance.cache-max-file-size: 2MB

performance.cache-size: 256MB

cluster.min-free-disk: 1%

nfs.disable: on

transport.address-family: inet

server.event-threads: 8

 

------

Hi Brandon,

 

Which options were removed?

 

Thanks,

Nithya  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190329/496fae4f/attachment.html>