Bug 1608396 - Rename for few files failed with "Transport endpoint is not connected" immediate after remove-brick commit
Summary: Rename for few files failed with "Transport endpoint is not connected" immedi...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Sanju
QA Contact: Bala Konda Reddy M
URL:
Whiteboard:
Depends On: 1470137
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-25 12:49 UTC by Prasad Desala
Modified: 2020-03-17 02:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Prasad Desala 2018-07-25 12:49:05 UTC
Description of problem:
=======================
When moving multiple temporary files to the same destination rename for few files failed with "Transport endpoint is not connected" immediate after remove-brick commit.

Version-Release number of selected component (if applicable):
3.12.2-14.el7rhgs.x86_64

How reproducible:
1/1

Steps to Reproduce:
===================
1) Create a distributed-replicated volume and start it.
2) FUSE mount it on multiple clients.
3) From few clients execute,

"while true; do uuid="`uuidgen`"; echo "some data" > "test$uuid"; mv "test$uuid" "test" -f; done"
From other clients, keep sending lookups.
4) Execute the script in step-3 for 10-15 mins.
5) Now remove few bricks and wait till the remove-brick completes.
6) Upon successful remove-brick start, perform remove-brick commit.

Actual results:
===============
Rename for few files failed with "Transport endpoint is not connected" immediate after remove-brick commit.

Expected results:
=================
Rename should not fail with "Transport endpoint is not connected" immediate after remove-brick commit.

Additional info:
================
sos reports and gluster-health-check will be shared.

Comment 3 Susant Kumar Palai 2018-08-02 13:04:33 UTC
Let me update this bug after analyzing the sos-reports.

Comment 4 Vivek Das 2018-08-12 15:32:54 UTC
Moving this bug out of 3.4.0 as it doesn't qualify blocker criteria and not proposed for 3.4.0. Please re-propose it for 3.4.0, if required.


Note You need to log in before you can comment on or make changes to this bug.