[HADOOP-8159] NetworkTopology: getLeaf should check for invalid topologies - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 1.1.0, 2.0.0-alpha
Component/s: None
Labels:
None

Hadoop Flags:

Reviewed

Description

Currently, in NetworkTopology, getLeaf doesn't do too much validation on the InnerNode object itself. This results in us getting ClassCastException sometimes when the network topology is invalid. We should have a less confusing exception message for this case.

Attachments

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

Attachments

HADOOP-8159-b1.005.patch
14/Mar/12 21:13
6 kB
Colin McCabe
HADOOP-8159.005.patch
14/Mar/12 21:24
7 kB
Colin McCabe
HADOOP-8159.006.patch
16/Mar/12 05:46
7 kB
Colin McCabe
HADOOP-8159.007.patch
20/Mar/12 21:20
4 kB
Colin McCabe
HADOOP-8159.008.patch
22/Mar/12 19:44
4 kB
Colin McCabe
HADOOP-8159.009.patch
22/Mar/12 21:44
2 kB
Colin McCabe
HADOOP-8159-b1.007.patch
22/Mar/12 23:03
2 kB
Colin McCabe

Issue Links

is related to

HADOOP-12173 NetworkTopology#add calls NetworkTopology#toString always

Resolved

relates to

HDFS-3129 NetworkTopology: add test that getLeaf should check for invalid topologies

Closed

Activity

People

Assignee:

Colin McCabe

Reporter:

Colin McCabe

Votes:

0 Vote for this issue

Watchers:

4 Start watching this issue

Dates

Created:

10/Mar/12 01:06

Updated:

04/Jul/15 00:09

Resolved:

26/Mar/12 22:20