[HDFS-6995] Block should be placed in the client's 'rack-local' node if 'client-local' node is not available - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 2.5.0
Fix Version/s: 2.6.0
Component/s: namenode
Labels:
None

Hadoop Flags:

Reviewed

Description

HDFS cluster is rack aware.
Client is in different node than of datanode,
but Same rack contains one or more datanodes.

In this case first preference should be given to select 'rack-local' node.

Currently, since no Node in clusterMap corresponds to client's location, blockplacement policy choosing a random node as local node and proceeding for further placements.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

HDFS-6995-001.patch
04/Sep/14 09:40
13 kB
Vinayakumar B
HDFS-6995-002.patch
05/Sep/14 04:33
15 kB
Vinayakumar B
HDFS-6995-003.patch
18/Sep/14 17:54
15 kB
Vinayakumar B
HDFS-6995-004.patch
19/Sep/14 07:50
16 kB
Vinayakumar B
HDFS-6995-005.patch
22/Sep/14 06:44
17 kB
Vinayakumar B
HDFS-6995-006.patch
29/Sep/14 06:24
17 kB
Vinayakumar B
HDFS-6995-007.patch
30/Sep/14 08:25
17 kB
Vinayakumar B

Issue Links

depends upon

HADOOP-10131 NetWorkTopology#countNumOfAvailableNodes() is returning wrong value if excluded nodes passed are not part of the cluster tree

Closed

duplicates

HDFS-5801 HDFS rack-awareness for nodes outside of the cluster

Closed

Activity

People

Assignee:: Vinayakumar B

Reporter:: Vinayakumar B

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Dates

Created:: 04/Sep/14 09:38

Updated:: 01/Dec/14 03:11

Resolved:: 06/Oct/14 09:07