Replies: 2 comments 3 replies
|
Yes, mfsclient acts as proxy for tools, mfsdirinfo included. |
|
@chogata |
|
This was how it worked in version 1.0 :) We changed that model - for a reason. The client keeps an open connection to the master, a tool opens a new connection every time it is run. Users killed the master when they run big shell loops calling tools many times inside. Of course, one could supply a tool that connects directly to the master and just comes with warnings, the problem is - users rarely read the warnings and then they ask "why is the tool killing my master?". So this change was made for safety/efficiency purposes. |
|
thank you for the explanation |
Uh oh!
There was an error while loading. Please reload this page.
I don't seem to find an option to specify the server or port.
I am trying to find out which of my moose folders started growing, and I am trying to use a docker container to send some data to influxdb. connecting remotely to master would be a perfect solution.
I can do simple ls, but mfsdirinfo has much more interesting info.
when trying to run mfsdirinfo from within the container (moosefs path mapped), I get
can't connect to master: EINPROGRESS (Operation now in progress)it looks like mfsdirinfo might be actually querying the mount process
All reactions