Description of problem: when enabling and disabling, performance translator( any of the following: md-cache/stat-prefetch, quick-read, io-cache, read-ahead, write-behind ) repeatedly for about an hour, causes error - "Transport endpoint is not connected" Version-Release number of selected component (if applicable): RHS 2.0.z How reproducible: consistently reproducible Steps to Reproduce: 1. Disable performance translator ( any of the following: md-cache/stat-prefetch, quick-read, io-cache, read-ahead, write-behind ) 2. After time interval of 5 seconds, again enable the same performance translator, disabled in step 1 3. Repeat the above procedure(step 1 and step 2), repeatedly for an hour Actual results: Getting error - "Transport endpoint not connected" after sometime Expected results: There should not be any error at the mount point - when performing any read/write operation Additional info: Above said error popped out after running the enable-disable cycle for over 21 minutes
after lock-migration, it should be seemless.
Verified this bug on release glusterfs 3.4.0qa4. Moving this bug to VERIFIED state
Retargeting for 2.1.z U2 (Corbett) release.
Du, Can you please verify the edited doc text for technical accuracy?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0208.html