[jira] Commented: (HBASE-3413) DNS Configs may completely break HBase cluster

2011-01-05 Thread ryan rawson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977685#action_12977685 ] ryan rawson commented on HBASE-3413: how would we ensure the uuid would be generated

[jira] Commented: (HBASE-3413) DNS Configs may completely break HBase cluster

2011-01-05 Thread Mathias Herberts (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977689#action_12977689 ] Mathias Herberts commented on HBASE-3413: - The idea of using a UUID was to be able

[jira] Created: (HBASE-3415) When scanners have readers updated we should use original file selection algorithm rather than include all files

2011-01-05 Thread Jonathan Gray (JIRA)
When scanners have readers updated we should use original file selection algorithm rather than include all files Key: HBASE-3415 URL:

[jira] Updated: (HBASE-3415) When scanners have readers updated we should use original file selection algorithm rather than include all files

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gray updated HBASE-3415: - Attachment: HBASE-3415-v1.patch First go. There are other bugs in this code and updating

[jira] Created: (HBASE-3416) For intra-row scanning, the update readers notification resets the query matcher and can lead to incorrect behavior

2011-01-05 Thread Jonathan Gray (JIRA)
For intra-row scanning, the update readers notification resets the query matcher and can lead to incorrect behavior --- Key: HBASE-3416 URL:

[jira] Created: (HBASE-3417) CacheOnWrite is using the temporary output path for block names, need to use a more consistent block naming scheme

2011-01-05 Thread Jonathan Gray (JIRA)
CacheOnWrite is using the temporary output path for block names, need to use a more consistent block naming scheme -- Key: HBASE-3417 URL:

[jira] Commented: (HBASE-3415) When scanners have readers updated we should use original file selection algorithm rather than include all files

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977815#action_12977815 ] stack commented on HBASE-3415: -- Am I missing something? You remove the getScanner(scan,

[jira] Updated: (HBASE-3406) Region stuck in transition after RS failed while opening

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-3406: - Fix Version/s: (was: 0.90.0) 0.90.1 Moving to 0.90.1 I cannot explain how in-memory

[jira] Created: (HBASE-3418) Increment operations can break when qualifiers are split between memstore/snapshot and storefiles

2011-01-05 Thread Jonathan Gray (JIRA)
Increment operations can break when qualifiers are split between memstore/snapshot and storefiles - Key: HBASE-3418 URL:

[jira] Updated: (HBASE-3418) Increment operations can break when qualifiers are split between memstore/snapshot and storefiles

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gray updated HBASE-3418: - Attachment: HBASE-3418-v1.patch Unit test which reproduces bad behavior and small fix which

[jira] Commented: (HBASE-3418) Increment operations can break when qualifiers are split between memstore/snapshot and storefiles

2011-01-05 Thread Todd Lipcon (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977864#action_12977864 ] Todd Lipcon commented on HBASE-3418: Can we put this in 0.90? seems like inaccurate

[jira] Updated: (HBASE-3418) Increment operations can break when qualifiers are split between memstore/snapshot and storefiles

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gray updated HBASE-3418: - Fix Version/s: (was: 0.90.1) 0.90.0 Yeah, looks like we're doing at least

[jira] Created: (HBASE-3419) If re-transition to OPENING during log replay fails, server aborts. Instead, should just cancel region open.

2011-01-05 Thread Jonathan Gray (JIRA)
If re-transition to OPENING during log replay fails, server aborts. Instead, should just cancel region open. - Key: HBASE-3419 URL:

[jira] Commented: (HBASE-3419) If re-transition to OPENING during log replay fails, server aborts. Instead, should just cancel region open.

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977870#action_12977870 ] Jonathan Gray commented on HBASE-3419: -- Currently the tickle happens on a

[jira] Created: (HBASE-3420) Handling a big rebalance, we can queue multiple instances of a Close event; messes up state

2011-01-05 Thread stack (JIRA)
Handling a big rebalance, we can queue multiple instances of a Close event; messes up state --- Key: HBASE-3420 URL: https://issues.apache.org/jira/browse/HBASE-3420

[jira] Resolved: (HBASE-3412) HLogSplitter should handle missing HLogs

2011-01-05 Thread Jean-Daniel Cryans (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Daniel Cryans resolved HBASE-3412. --- Resolution: Fixed Assignee: Jean-Daniel Cryans Hadoop Flags: [Reviewed]

[jira] Commented: (HBASE-3420) Handling a big rebalance, we can queue multiple instances of a Close event; messes up state

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977890#action_12977890 ] stack commented on HBASE-3420: -- Its timeout of a close. Here is sequence: {code} 2011-01-05

[jira] Commented: (HBASE-3418) Increment operations can break when qualifiers are split between memstore/snapshot and storefiles

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977896#action_12977896 ] stack commented on HBASE-3418: -- +1 on patch. Increment operations can break when qualifiers

[jira] Commented: (HBASE-3420) Handling a big rebalance, we can queue multiple instances of a Close event; messes up state

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977897#action_12977897 ] stack commented on HBASE-3420: -- Looking more, the CLOSED event had been queued over on the

[jira] Updated: (HBASE-3420) Handling a big rebalance, we can queue multiple instances of a Close event; messes up state

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-3420: - Attachment: 3420.txt This should address most egregious issue turned up by these logs. Other things to add are

[jira] Commented: (HBASE-3420) Handling a big rebalance, we can queue multiple instances of a Close event; messes up state

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977906#action_12977906 ] Jonathan Gray commented on HBASE-3420: -- So this just updates the timestamp. Seems

[jira] Commented: (HBASE-3420) Handling a big rebalance, we can queue multiple instances of a Close event; messes up state

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977929#action_12977929 ] stack commented on HBASE-3420: -- @Ted Balancing works differently in 0.90. Where before, when

[jira] Commented: (HBASE-3420) Handling a big rebalance, we can queue multiple instances of a Close event; messes up state

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977930#action_12977930 ] Jonathan Gray commented on HBASE-3420: -- It's unrelated to the notion of checkins

[jira] Commented: (HBASE-3417) CacheOnWrite is using the temporary output path for block names, need to use a more consistent block naming scheme

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977943#action_12977943 ] Jonathan Gray commented on HBASE-3417: -- One idea from discussion with stack is to use

[jira] Commented: (HBASE-3420) Handling a big rebalance, we can queue multiple instances of a Close event; messes up state

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977968#action_12977968 ] stack commented on HBASE-3420: -- Ok... with this patch in place, master was able to join the

[jira] Resolved: (HBASE-3420) Handling a big rebalance, we can queue multiple instances of a Close event; messes up state

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-3420. -- Resolution: Fixed Fix Version/s: (was: 0.90.1) 0.90.0 Assignee: stack

[jira] Created: (HBASE-3421) Very wide rows -- 30M plus -- cause us OOME

2011-01-05 Thread stack (JIRA)
Very wide rows -- 30M plus -- cause us OOME --- Key: HBASE-3421 URL: https://issues.apache.org/jira/browse/HBASE-3421 Project: HBase Issue Type: Bug Affects Versions: 0.90.0 Reporter:

[jira] Created: (HBASE-3422) Balancer will willing try to rebalance thousands of regions in one go; needs an upper bound added.

2011-01-05 Thread stack (JIRA)
Balancer will willing try to rebalance thousands of regions in one go; needs an upper bound added. -- Key: HBASE-3422 URL:

[jira] Commented: (HBASE-3409) Failed server shutdown processing when retrying hlog split

2011-01-05 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977981#action_12977981 ] Hudson commented on HBASE-3409: --- Integrated in HBase-TRUNK #1703 (See

[jira] Commented: (HBASE-3412) HLogSplitter should handle missing HLogs

2011-01-05 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977978#action_12977978 ] Hudson commented on HBASE-3412: --- Integrated in HBase-TRUNK #1703 (See

[jira] Commented: (HBASE-3402) Web UI shows two META regions

2011-01-05 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977979#action_12977979 ] Hudson commented on HBASE-3402: --- Integrated in HBase-TRUNK #1703 (See

[jira] Commented: (HBASE-3419) If re-transition to OPENING during log replay fails, server aborts. Instead, should just cancel region open.

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977983#action_12977983 ] stack commented on HBASE-3419: -- Chatting about this up on IRC, the tickle does not happen if

[jira] Assigned: (HBASE-3419) If re-transition to OPENING during log replay fails, server aborts. Instead, should just cancel region open.

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gray reassigned HBASE-3419: Assignee: Jonathan Gray Working on implementing what stack outlined above. If

[jira] Commented: (HBASE-3421) Very wide rows -- 30M plus -- cause us OOME

2011-01-05 Thread Nicolas Spiegelberg (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978016#action_12978016 ] Nicolas Spiegelberg commented on HBASE-3421: Note that you can limit the number

[jira] Updated: (HBASE-3419) If re-transition to OPENING during log replay fails, server aborts. Instead, should just cancel region open.

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gray updated HBASE-3419: - Attachment: HBASE-3419-v1.patch As outlined. Had to add new {{CancelableProgressable}}

[jira] Commented: (HBASE-3403) Region orphaned after failure during split

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978035#action_12978035 ] stack commented on HBASE-3403: -- bq. + cluster.getMaster().catalogJanitorSwitch(false); I

[jira] Updated: (HBASE-3419) If re-transition to OPENING during log replay fails, server aborts. Instead, should just cancel region open.

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gray updated HBASE-3419: - Attachment: HBASE-3419-v2.patch Squashed the v1 patch with another patch. v2 is just this

[jira] Commented: (HBASE-3421) Very wide rows -- 30M plus -- cause us OOME

2011-01-05 Thread Nicolas Spiegelberg (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978054#action_12978054 ] Nicolas Spiegelberg commented on HBASE-3421: For interested parties... From:

[jira] Updated: (HBASE-3417) CacheOnWrite is using the temporary output path for block names, need to use a more consistent block naming scheme

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gray updated HBASE-3417: - Attachment: HBASE-3417-v1.patch Changes storefile names to be UUIDs. Makes it so we use the

[jira] Created: (HBASE-3423) hbase-env.sh over-rides HBASE_OPTS incorrectly.

2011-01-05 Thread Ted Dunning (JIRA)
hbase-env.sh over-rides HBASE_OPTS incorrectly. --- Key: HBASE-3423 URL: https://issues.apache.org/jira/browse/HBASE-3423 Project: HBase Issue Type: Bug Affects Versions: 0.90.0

[jira] Updated: (HBASE-3417) CacheOnWrite is using the temporary output path for block names, need to use a more consistent block naming scheme

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gray updated HBASE-3417: - Attachment: HBASE-3417-v2.patch Makes it so we don't have to parse fileName for each block when

[jira] Commented: (HBASE-3417) CacheOnWrite is using the temporary output path for block names, need to use a more consistent block naming scheme

2011-01-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978122#action_12978122 ] stack commented on HBASE-3417: -- As discussed up on IRC, this is not backward compatible:

[jira] Commented: (HBASE-3417) CacheOnWrite is using the temporary output path for block names, need to use a more consistent block naming scheme

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978124#action_12978124 ] Jonathan Gray commented on HBASE-3417: -- I changed regex to be {{([0-9a-z]+)}} I kind

[jira] Commented: (HBASE-3417) CacheOnWrite is using the temporary output path for block names, need to use a more consistent block naming scheme

2011-01-05 Thread Jonathan Gray (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978125#action_12978125 ] Jonathan Gray commented on HBASE-3417: -- Old random file name was using rand.nextLong()

[jira] Commented: (HBASE-3420) Handling a big rebalance, we can queue multiple instances of a Close event; messes up state

2011-01-05 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978156#action_12978156 ] Hudson commented on HBASE-3420: --- Integrated in HBase-TRUNK #1705 (See

[jira] Commented: (HBASE-3423) hbase-env.sh over-rides HBASE_OPTS incorrectly.

2011-01-05 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978157#action_12978157 ] Hudson commented on HBASE-3423: --- Integrated in HBase-TRUNK #1705 (See

[jira] Commented: (HBASE-3379) Log splitting slowed by repeated attempts at connecting to downed datanode

2011-01-05 Thread Hairong Kuang (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978160#action_12978160 ] Hairong Kuang commented on HBASE-3379: -- Stack, HBASE-3285 should be able to fix the