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
[
https://issues.apache.org/jira/browse/HBASE-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13558517#comment-13558517
]
Feng Honghua commented on HBASE-7632:
-
The root cause is when client/shell add_peer,
[
https://issues.apache.org/jira/browse/HBASE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527752#comment-13527752
]
Feng Honghua commented on HBASE-7280:
-
Thanks Jean-Daniel
But even REPLICATION_SCOPE
[
https://issues.apache.org/jira/browse/HBASE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13511021#comment-13511021
]
Feng Honghua commented on HBASE-7280:
-
I can understand the initiative of current
[
https://issues.apache.org/jira/browse/HBASE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13511076#comment-13511076
]
Feng Honghua commented on HBASE-7280:
-
yes, that's what I hope for the finer-grained
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.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
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: HBase
[
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
[
https://issues.apache.org/jira/browse/HBASE-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505236#comment-13505236
]
Feng Honghua commented on HBASE-7226:
-
the same typo bug exists for trunk as well
[
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
[
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
501 - 512 of 512 matches
Mail list logo