cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mck (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6091) Better Vnode support in hadoop/pig
Date Sat, 11 Oct 2014 22:22:34 GMT


mck commented on CASSANDRA-6091:

[~alexliu68] Any reason we can't (at least to begin with since this is a right headache) join
the splits after the call to describe_splits_ex, as is done in this [patch|]?

Although one thing about this patch that i haven't yet understood, when i test against a single-node
cluster i expect rejoinAdjacentSplits(..) to return a list of one split, token range "-8940796744825771419"
to "6948181744525544", but instead i get that plus two more splits, in total three splits
that look like

 1) "-8940796744825771419" to "6948181744525544"
 2) "-1" to "-8940796744825771419"
 3) "6948181744525544" to "-8940796744825771419"

This is highlighted by the assert statement commented out in ACFIF line 253 
Am i doing something wrong or is describe_local_ring?

> Better Vnode support in hadoop/pig
> ----------------------------------
>                 Key: CASSANDRA-6091
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>            Reporter: Alex Liu
>            Assignee: Alex Liu
> CASSANDRA-6084 shows there are some issues during running hadoop/pig job if vnodes are
enable. Also the hadoop performance of vnode enabled nodes  are bad for there are so many
> The idea is to combine vnode splits into a big sudo splits so it work like vnode is disable
for hadoop/pig job

This message was sent by Atlassian JIRA

View raw message