[Moosefs-users] system high load when file has error

[Anh K. H. <anh...@gm...>]

Hi,

On the webUI, I can see the error

   currently unavailable chunk 0000000000139D7E
     (inode: 870852 ; index: 0)
   - currently unavailable file in trash 870852: foobar/bin/sam
     unavailable chunks: 1
     unavailable trash files: 1

As you can see, there is only one minor problem, but the cause is
weird / critical: The original file 'foobar/bin/sam' is inaccessible in
a loop-way: When my problem accesses the file, it waits forever, and I
have to press "^C" or to use "kill -9" to close the connection. This may
be possible, but if the program runs in background, system won't know
how to kill it, and system load will be very high . (In the mean time, I
delete the file so you see it reported in "trash", and get a new
version of file to use for my background tasks.)

My question is: Is there any way to force client to exit when they try
to access an error file in a MFS directory?

There is also a similar problem when the mfsmaster is down: All
mfsclients' system load will be (VERY) high. In an ideal condition, the
clients should be unmounted before the master is shut down, but for some
reasons, if the network / master has problem, the client should be
smart enough to disconnect from the master automatically.

Thank you very much.

Regards,

-- 
There seems no plan because it is all plan.
		-- C.S. Lewis