Bug 1212377

Summary:	"Transport Endpoint Error" seen when hot tier is unavailable
Product:	[Community] GlusterFS	Reporter:	Anoop <annair>
Component:	tiering	Assignee:	Dan Lambright <dlambrig>
Status:	CLOSED NOTABUG	QA Contact:	bugs <bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, nchilaka
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-14 06:47:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1186580, 1199352, 1260923

Description Anoop 2015-04-16 09:47:04 UTC

Description of problem:

Seeing "transport endpoint error" on copying files when the the hot tier in unavailable

Version-Release number of selected component (if applicable):
glusterfs-server-3.7dev-0.885.git0d36d4f.el6.x86_64


Volume Name: tiervol
Type: Tier
Volume ID: 3744cb8f-c6a2-4d31-b034-9c590989118a
Status: Started
Number of Bricks: 2 x 1 = 2
Transport-type: tcp
Bricks:
Brick1: 10.70.35.166:/b5

 
Steps to Reproduce:
1. Create a simple distributed volume 
2. Attach another distribute (as hot tier) to the created volume
3. Mount the volume on the client
4. Kill the brick process for the hot tier
5. Initiate copy of data in the mount
6. Seeing "Transport endpoint is not connected" error on copy

Expected Result:
Even if the hot tier is down, the copy should continue on the cold tier.

Comment 1 Dan Lambright 2015-04-22 15:43:17 UTC

This bug is unclear. We need to know if the file resides on the hot tier or the cold tier.

If the file existed on the hot tier, it will not be available when you kill the brick process. A file only exists on one tier, not both.

If the file exists on the cold tier, it would be available, and we would chase it. 

Probably the best way to document this would be including in the bug 

ls /brick_hot
and
ls /brick_cold

We can discuss more to drill down. 

For now I'll put this bug in ON_QA pending our discussion.

Comment 2 Anoop 2015-05-13 12:43:54 UTC

This is for fresh writes. All fresh writes are failing when hot tier is unavailable. 
Reproduced this ont the BETA2 build too, hence moving it to ASSIGNED.

Comment 3 Dan Lambright 2015-05-14 06:47:15 UTC

Even if it is a fresh write we cannot create a new file. We cannot know if the file already exists on the hot tier. If it turned out the file did already exist, and we created a second file with the same name on the cold, this would overwrite the old file and be dataloss. This is not a bug.