Yes it could as depending on number of bricks there might be too many brick ops involved. This is the reason we introduced --timeout option in CLI which can be used to have a larger time out value. However this fix is available from release-3.9 onwards.
On Mon, Jul 24, 2017 at 3:54 PM, lejeczek <[email protected]> wrote: > hi fellas > > would you know what could be the problem with: vol status detail times out > always? > After I did above I had to restart glusterd on the peer which had the > command issued. > I run 3.8.14. Everything seems to work a ok. > > many thanks > L. > _______________________________________________ > Gluster-users mailing list > [email protected] > http://lists.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list [email protected] http://lists.gluster.org/mailman/listinfo/gluster-users
