[jira] [Commented] (HBASE-7632) fail to create ReplicationSource if ReplicationPeer.startStateTracker checkExists(peerStateNode) and find not exist but fails in createAndWatch due to client/shell is d

2013-01-20 Thread Feng Honghua (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558517#comment-13558517 ] Feng Honghua commented on HBASE-7632: - The root cause is when client/shell add_peer, i

[jira] [Commented] (HBASE-7632) fail to create ReplicationSource if ReplicationPeer.startStateTracker checkExists(peerStateNode) and find not exist but fails in createAndWatch due to client/shell is d

2013-01-20 Thread Feng Honghua (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558511#comment-13558511 ] Feng Honghua commented on HBASE-7632: - attach the call stack: 2013-01-10 09:22:03,084

[jira] [Created] (HBASE-7632) fail to create ReplicationSource if ReplicationPeer.startStateTracker checkExists(peerStateNode) and find not exist but fails in createAndWatch due to client/shell is don

2013-01-20 Thread Feng Honghua (JIRA)
Feng Honghua created HBASE-7632: --- Summary: fail to create ReplicationSource if ReplicationPeer.startStateTracker checkExists(peerStateNode) and find not exist but fails in createAndWatch due to client/shell is done creating it then, now throws exc

[jira] [Commented] (HBASE-7280) TableNotFoundException thrown in peer cluster will incur endless retry for shipEdits, which in turn block following normal replication

2012-12-09 Thread Feng Honghua (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527752#comment-13527752 ] Feng Honghua commented on HBASE-7280: - Thanks Jean-Daniel But even REPLICATION_SCOPE

[jira] [Commented] (HBASE-7280) TableNotFoundException thrown in peer cluster will incur endless retry for shipEdits, which in turn block following normal replication

2012-12-05 Thread Feng Honghua (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511076#comment-13511076 ] Feng Honghua commented on HBASE-7280: - yes, that's what I hope for the finer-grained c

[jira] [Commented] (HBASE-7280) TableNotFoundException thrown in peer cluster will incur endless retry for shipEdits, which in turn block following normal replication

2012-12-05 Thread Feng Honghua (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511021#comment-13511021 ] Feng Honghua commented on HBASE-7280: - I can understand the initiative of current desi

[jira] [Created] (HBASE-7280) TableNotFoundException thrown in peer cluster will incur endless retry for shipEdits, which in turn block following normal replication

2012-12-04 Thread Feng Honghua (JIRA)
Feng Honghua created HBASE-7280: --- Summary: TableNotFoundException thrown in peer cluster will incur endless retry for shipEdits, which in turn block following normal replication Key: HBASE-7280 URL: https://issues.a

[jira] [Updated] (HBASE-7226) HRegion.checkAndMutate uses incorrect comparison result for <, <=, > and >=

2012-11-27 Thread Feng Honghua (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-7226: Attachment: (was: checkAndMutate.patch) > HRegion.checkAndMutate uses incorrect comparison

[jira] [Updated] (HBASE-7226) HRegion.checkAndMutate uses incorrect comparison result for <, <=, > and >=

2012-11-27 Thread Feng Honghua (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-7226: Attachment: HRegion_HBASE_7226_0.94.2.patch > HRegion.checkAndMutate uses incorrect comparison

[jira] [Commented] (HBASE-7226) HRegion.checkAndMutate uses incorrect comparison result for <, <=, > and >=

2012-11-27 Thread Feng Honghua (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505236#comment-13505236 ] Feng Honghua commented on HBASE-7226: - the same typo bug exists for trunk as well

[jira] [Updated] (HBASE-7226) HRegion.checkAndMutate uses incorrect comparison result for <, <=, > and >=

2012-11-27 Thread Feng Honghua (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-7226: Attachment: checkAndMutate.patch > HRegion.checkAndMutate uses incorrect comparison result for

[jira] [Updated] (HBASE-7226) HRegion.checkAndMutate uses incorrect comparison result for <, <=, > and >=

2012-11-27 Thread Feng Honghua (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-7226: Status: Patch Available (was: Open) > HRegion.checkAndMutate uses incorrect comparison result

[jira] [Created] (HBASE-7226) HRegion.checkAndMutate uses incorrect comparison result for <, <=, > and >=

2012-11-27 Thread Feng Honghua (JIRA)
Feng Honghua created HBASE-7226: --- Summary: HRegion.checkAndMutate uses incorrect comparison result for <, <=, > and >= Key: HBASE-7226 URL: https://issues.apache.org/jira/browse/HBASE-7226 Project: HBas

<    1   2   3   4   5   6