[jira] [Commented] (HBASE-13819) Make RPC layer CellBlock buffer a DirectByteBuffer

[ https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282372#comment-16282372 ] huaxiang sun commented on HBASE-13819: -- Thanks [~anoop.hbase] for explaining the BBPool in 2.0, so

[jira] [Commented] (HBASE-19364) Truncate_preserve fails with table when replica region > 1

[ https://issues.apache.org/jira/browse/HBASE-19364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282263#comment-16282263 ] huaxiang sun commented on HBASE-19364: -- Thanks [~pankaj2461], I will review shortly. >

[jira] [Commented] (HBASE-13819) Make RPC layer CellBlock buffer a DirectByteBuffer

[ https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280599#comment-16280599 ] huaxiang sun commented on HBASE-13819: -- Thanks [~anoop.hbase]. With JDK-8147468, in NIO case, for

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279439#comment-16279439 ] huaxiang sun commented on HBASE-19163: -- Will commit tomorrow morning PST if no objection, thanks. >

[jira] [Comment Edited] (HBASE-13819) Make RPC layer CellBlock buffer a DirectByteBuffer

[ https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279306#comment-16279306 ] huaxiang sun edited comment on HBASE-13819 at 12/5/17 11:10 PM: Hi

[jira] [Commented] (HBASE-13819) Make RPC layer CellBlock buffer a DirectByteBuffer

[ https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279306#comment-16279306 ] huaxiang sun commented on HBASE-13819: -- Hi [~anoop.hbase], I am reading the patch and thought about

[jira] [Comment Edited] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279204#comment-16279204 ] huaxiang sun edited comment on HBASE-19163 at 12/5/17 9:35 PM: --- There are

[jira] [Commented] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279220#comment-16279220 ] huaxiang sun commented on HBASE-19320: -- The initial result from our testing result looks positive.

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279204#comment-16279204 ] huaxiang sun commented on HBASE-19163: -- There are so many testing failure due to the default

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.010.patch > "Maximum lock count exceeded" from region server's

[jira] [Assigned] (HBASE-18625) Splitting of region with replica, doesn't update region list in serverHolding. A server crash leads to overlap.

[ https://issues.apache.org/jira/browse/HBASE-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun reassigned HBASE-18625: Assignee: huaxiang sun > Splitting of region with replica, doesn't update region list in

[jira] [Commented] (HBASE-18625) Splitting of region with replica, doesn't update region list in serverHolding. A server crash leads to overlap.

[ https://issues.apache.org/jira/browse/HBASE-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16279096#comment-16279096 ] huaxiang sun commented on HBASE-18625: -- Take this over for now. [~igloo1986], please let me know if

[jira] [Commented] (HBASE-18625) Splitting of region with replica, doesn't update region list in serverHolding. A server crash leads to overlap.

[ https://issues.apache.org/jira/browse/HBASE-18625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277607#comment-16277607 ] huaxiang sun commented on HBASE-18625: -- Hi [~igloo1986], are you working on this issue? Do you mind

[jira] [Reopened] (HBASE-19392) TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master

[ https://issues.apache.org/jira/browse/HBASE-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun reopened HBASE-19392: -- The test has been better, but the flakey is still there. A different one, reopen the issue.

[jira] [Commented] (HBASE-19392) TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master

[ https://issues.apache.org/jira/browse/HBASE-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274524#comment-16274524 ] huaxiang sun commented on HBASE-19392: -- Thanks [~saint@gmail.com] and [~te...@apache.org] for

[jira] [Commented] (HBASE-19398) Unit Tests failed in hbase-3.0.0 on Arm64 and x86

[ https://issues.apache.org/jira/browse/HBASE-19398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274522#comment-16274522 ] huaxiang sun commented on HBASE-19398: -- Hi [~guyuqi], TestReplicaWithCluster should be fixed by

[jira] [Commented] (HBASE-19392) TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master

[ https://issues.apache.org/jira/browse/HBASE-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273719#comment-16273719 ] huaxiang sun commented on HBASE-19392: -- I run the unittest locally, it failed for me almost

[jira] [Updated] (HBASE-19392) TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master

[ https://issues.apache.org/jira/browse/HBASE-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19392: - Attachment: HBASE-19392-master-v001.patch >

[jira] [Commented] (HBASE-19392) TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master

[ https://issues.apache.org/jira/browse/HBASE-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273670#comment-16273670 ] huaxiang sun commented on HBASE-19392: -- Sorry, wrong patch attached! Will upload the correct one,

[jira] [Updated] (HBASE-19392) TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master

[ https://issues.apache.org/jira/browse/HBASE-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19392: - Attachment: (was: HBASE-19163.master.009.patch) >

[jira] [Updated] (HBASE-19392) TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master

[ https://issues.apache.org/jira/browse/HBASE-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19392: - Attachment: HBASE-19163.master.009.patch >

[jira] [Updated] (HBASE-19392) TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master

[ https://issues.apache.org/jira/browse/HBASE-19392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19392: - Status: Patch Available (was: Open) >

[jira] [Created] (HBASE-19392) TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master

huaxiang sun created HBASE-19392: Summary: TestReplicaWithCluster#testReplicaGetWithPrimaryAndMetaDown failure in master Key: HBASE-19392 URL: https://issues.apache.org/jira/browse/HBASE-19392

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.009.patch > "Maximum lock count exceeded" from region server's

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271841#comment-16271841 ] huaxiang sun commented on HBASE-19163: -- I saw a few flakey ones, submit for another run. > "Maximum

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16269938#comment-16269938 ] huaxiang sun commented on HBASE-19163: -- TestFlushSnapshotFromClient failure is similar and I

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.009.patch > "Maximum lock count exceeded" from region server's

[jira] [Created] (HBASE-19365) FSTableDescriptors#get() can return null reference, in some cases, it is not checked

huaxiang sun created HBASE-19365: Summary: FSTableDescriptors#get() can return null reference, in some cases, it is not checked Key: HBASE-19365 URL: https://issues.apache.org/jira/browse/HBASE-19365

[jira] [Commented] (HBASE-19364) Truncate_preserve fails with table when replica region > 1

[ https://issues.apache.org/jira/browse/HBASE-19364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16269080#comment-16269080 ] huaxiang sun commented on HBASE-19364: -- Thanks [~pankaj2461] for reporting the issue. Could you post

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16269061#comment-16269061 ] huaxiang sun commented on HBASE-19163: -- The unit failure is related, I uploaded a new patch to fix

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.008.patch > "Maximum lock count exceeded" from region server's

[jira] [Commented] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16269052#comment-16269052 ] huaxiang sun commented on HBASE-19320: -- Thanks [~anoop.hbase] for confirm. Hi [~ashishujjain],

[jira] [Commented] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267824#comment-16267824 ] huaxiang sun commented on HBASE-19320: -- I went through the off-heap docs briefly. I think the answer

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267294#comment-16267294 ] huaxiang sun commented on HBASE-19163: -- Thanks [~saint@gmail.com]. I uploaded a new patch which

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.007.patch > "Maximum lock count exceeded" from region server's

[jira] [Commented] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267189#comment-16267189 ] huaxiang sun commented on HBASE-19320: -- Sorry for the late response, [~anoop.hbase] and

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264682#comment-16264682 ] huaxiang sun commented on HBASE-19163: -- Yes, [~saint@gmail.com]. The issue is filed,

[jira] [Commented] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261852#comment-16261852 ] huaxiang sun commented on HBASE-19320: -- The fix is in jdk8u102 and jdk9, FYI.

[jira] [Commented] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261849#comment-16261849 ] huaxiang sun commented on HBASE-19320: -- That is great to learn [~Apache9]! Netty by default for 2.0?

[jira] [Commented] (HBASE-16137) Fix findbugs warning introduced by hbase-14730

[ https://issues.apache.org/jira/browse/HBASE-16137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261793#comment-16261793 ] huaxiang sun commented on HBASE-16137: -- Hi [~psomogyi], I assign this jira to you, thanks! > Fix

[jira] [Assigned] (HBASE-16137) Fix findbugs warning introduced by hbase-14730

[ https://issues.apache.org/jira/browse/HBASE-16137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun reassigned HBASE-16137: Assignee: Peter Somogyi (was: huaxiang sun) > Fix findbugs warning introduced by

[jira] [Comment Edited] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261779#comment-16261779 ] huaxiang sun edited comment on HBASE-19320 at 11/22/17 12:52 AM: - Attach

[jira] [Comment Edited] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261779#comment-16261779 ] huaxiang sun edited comment on HBASE-19320 at 11/22/17 12:51 AM: - Attach

[jira] [Commented] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261779#comment-16261779 ] huaxiang sun commented on HBASE-19320: -- Attach two screenshots for this issue. The first one is

[jira] [Updated] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19320: - Attachment: Screen Shot 2017-11-21 at 4.43.36 PM.png Screen Shot 2017-11-21 at

[jira] [Updated] (HBASE-19320) document the mysterious direct memory leak in hbase

[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19320: - Affects Version/s: 1.2.6 > document the mysterious direct memory leak in hbase >

[jira] [Created] (HBASE-19320) document the mysterious direct memory leak in hbase

huaxiang sun created HBASE-19320: Summary: document the mysterious direct memory leak in hbase Key: HBASE-19320 URL: https://issues.apache.org/jira/browse/HBASE-19320 Project: HBase Issue

[jira] [Updated] (HBASE-19308) batch processing does not consider partial success

[ https://issues.apache.org/jira/browse/HBASE-19308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19308: - Fix Version/s: 2.0.0 > batch processing does not consider partial success >

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259945#comment-16259945 ] huaxiang sun commented on HBASE-19163: -- Post another patch to address unittest failures.

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.006.patch > "Maximum lock count exceeded" from region server's

[jira] [Commented] (HBASE-19308) batch processing does not consider partial success

[ https://issues.apache.org/jira/browse/HBASE-19308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259831#comment-16259831 ] huaxiang sun commented on HBASE-19308: -- I will upload an unitest case in HBASE-19163. > batch

[jira] [Created] (HBASE-19308) batch processing does not consider partial success

huaxiang sun created HBASE-19308: Summary: batch processing does not consider partial success Key: HBASE-19308 URL: https://issues.apache.org/jira/browse/HBASE-19308 Project: HBase Issue

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259823#comment-16259823 ] huaxiang sun commented on HBASE-19163: -- The testing failures expose an interesting issue (critical?)

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259786#comment-16259786 ] huaxiang sun commented on HBASE-19163: -- Hi [~Allen_2891], a few concerns with hashmap approach. 1).

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259456#comment-16259456 ] huaxiang sun commented on HBASE-19163: -- Test failures are related, checking now. > "Maximum lock

[jira] [Comment Edited] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258931#comment-16258931 ] huaxiang sun edited comment on HBASE-19163 at 11/20/17 8:16 AM: Hi

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258931#comment-16258931 ] huaxiang sun commented on HBASE-19163: -- Hi [~saint@gmail.com] and [~allan163], I uploaded a new

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.005.patch > "Maximum lock count exceeded" from region server's

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258120#comment-16258120 ] huaxiang sun commented on HBASE-19163: -- Yeah [~allan163], that is a good idea. Let me cook up a new

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: (was: HBASE-19163.master.005.patch) > "Maximum lock count exceeded" from region

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.005.patch > "Maximum lock count exceeded" from region server's

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.004.patch > "Maximum lock count exceeded" from region server's

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257586#comment-16257586 ] huaxiang sun commented on HBASE-19163: -- The latest patch is v2, to avoid confusion, I deleted the

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: (was: HBASE-19163.master.003.patch) > "Maximum lock count exceeded" from region

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.002.patch > "Maximum lock count exceeded" from region server's

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256237#comment-16256237 ] huaxiang sun commented on HBASE-19163: -- v003 patch addresses Stack's concern about performance, so

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: (was: HBASE-19163.master.004.patch) > "Maximum lock count exceeded" from region

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: (was: HBASE-19163.master.002.patch) > "Maximum lock count exceeded" from region

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.004.patch > "Maximum lock count exceeded" from region server's

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.003.patch > "Maximum lock count exceeded" from region server's

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.002.patch > "Maximum lock count exceeded" from region server's

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163.master.001.patch > "Maximum lock count exceeded" from region server's

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254599#comment-16254599 ] huaxiang sun commented on HBASE-19163: -- Hi [~uagashe], thanks for the review. I will upload this to

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Affects Version/s: 3.0.0 2.0.0-alpha-3 > "Maximum lock count exceeded"

[jira] [Commented] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254488#comment-16254488 ] huaxiang sun commented on HBASE-19163: -- Right now, option 1 is implemented in the patch. There are

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Status: Patch Available (was: Open) > "Maximum lock count exceeded" from region server's batch

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: HBASE-19163-master-v001.patch attach v1 patch. > "Maximum lock count exceeded" from

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Attachment: unittest-case.diff add an unittest to explore the issue. > "Maximum lock count

[jira] [Commented] (HBASE-13850) Check for dead server on CallTimeoutException

[ https://issues.apache.org/jira/browse/HBASE-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240663#comment-16240663 ] huaxiang sun commented on HBASE-13850: -- We have one similar use case, will check, thanks. > Check

[jira] [Assigned] (HBASE-13850) Check for dead server on CallTimeoutException

[ https://issues.apache.org/jira/browse/HBASE-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun reassigned HBASE-13850: Assignee: huaxiang sun > Check for dead server on CallTimeoutException >

[jira] [Updated] (HBASE-19163) "Maximum lock count exceeded" from region server's batch processing

[ https://issues.apache.org/jira/browse/HBASE-19163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-19163: - Summary: "Maximum lock count exceeded" from region server's batch processing (was: "Maximum

[jira] [Created] (HBASE-19163) "Maximum Lock Acquired" from region server's batch processing

huaxiang sun created HBASE-19163: Summary: "Maximum Lock Acquired" from region server's batch processing Key: HBASE-19163 URL: https://issues.apache.org/jira/browse/HBASE-19163 Project: HBase

[jira] [Updated] (HBASE-18693) adding an option to restore_snapshot to move mob files from archive dir to working dir

[ https://issues.apache.org/jira/browse/HBASE-18693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-18693: - Attachment: HBASE-18693.master.003.patch Upload patch v3 to address TestShell failure. The other

[jira] [Commented] (HBASE-18352) Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614

[ https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16216369#comment-16216369 ] huaxiang sun commented on HBASE-18352: -- I noticed that, and even after I commented the code out in

[jira] [Commented] (HBASE-18352) Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614

[ https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215944#comment-16215944 ] huaxiang sun commented on HBASE-18352: -- [~ram_krish], with HBASE-18946_1.patch, the failed test

[jira] [Commented] (HBASE-18352) Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614

[ https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215581#comment-16215581 ] huaxiang sun commented on HBASE-18352: -- Great, [~ram_krish]! Let me try the patch out and report

[jira] [Commented] (HBASE-18352) Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614

[ https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215482#comment-16215482 ] huaxiang sun commented on HBASE-18352: -- Thanks Ram for looking into it as well. The above

[jira] [Commented] (HBASE-18352) Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614

[ https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214363#comment-16214363 ] huaxiang sun commented on HBASE-18352: -- Posting the progress so far,

[jira] [Commented] (HBASE-18946) Stochastic load balancer assigns replica regions to the same RS

[ https://issues.apache.org/jira/browse/HBASE-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211811#comment-16211811 ] huaxiang sun commented on HBASE-18946: -- For the case with increased replica count, even with

[jira] [Commented] (HBASE-18946) Stochastic load balancer assigns replica regions to the same RS

[ https://issues.apache.org/jira/browse/HBASE-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211449#comment-16211449 ] huaxiang sun commented on HBASE-18946: -- Thanks [~ram_krish]. One possible slowdown here with the

[jira] [Commented] (HBASE-18946) Stochastic load balancer assigns replica regions to the same RS

[ https://issues.apache.org/jira/browse/HBASE-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208547#comment-16208547 ] huaxiang sun commented on HBASE-18946: -- Do we need to apply the same collection logic to

[jira] [Commented] (HBASE-19017) EnableTableProcedure is not retaining the assignments

[ https://issues.apache.org/jira/browse/HBASE-19017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206753#comment-16206753 ] huaxiang sun commented on HBASE-19017: -- +1 > EnableTableProcedure is not retaining the assignments

[jira] [Commented] (HBASE-18946) Stochastic load balancer assigns replica regions to the same RS

[ https://issues.apache.org/jira/browse/HBASE-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206684#comment-16206684 ] huaxiang sun commented on HBASE-18946: -- Sorry, [~ramkrishna], busy with something else. going

[jira] [Commented] (HBASE-18693) adding an option to restore_snapshot to move mob files from archive dir to working dir

[ https://issues.apache.org/jira/browse/HBASE-18693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206319#comment-16206319 ] huaxiang sun commented on HBASE-18693: -- I am checking these failed unittests locally and will do

[jira] [Commented] (HBASE-18693) adding an option to restore_snapshot to move mob files from archive dir to working dir

[ https://issues.apache.org/jira/browse/HBASE-18693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206304#comment-16206304 ] huaxiang sun commented on HBASE-18693: -- @tedyu and [~jingcheng.du], I posted v2 at the review board,

[jira] [Updated] (HBASE-18355) Enable export snapshot tests that were disabled by Proc-V2 AM in HBASE-14614

[ https://issues.apache.org/jira/browse/HBASE-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun updated HBASE-18355: - Resolution: Fixed Fix Version/s: 2.0.0-alpha-4 3.0.0 Status:

[jira] [Commented] (HBASE-18355) Enable export snapshot tests that were disabled by Proc-V2 AM in HBASE-14614

[ https://issues.apache.org/jira/browse/HBASE-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204237#comment-16204237 ] huaxiang sun commented on HBASE-18355: -- Thanks [~tedyu] and [~mdrob] for review! I pushed the patch

[jira] [Assigned] (HBASE-18352) Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614

[ https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun reassigned HBASE-18352: Assignee: huaxiang sun (was: Vladimir Rodionov) > Enable Replica tests that were

[jira] [Commented] (HBASE-18352) Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614

[ https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203917#comment-16203917 ] huaxiang sun commented on HBASE-18352: -- Thanks! > Enable Replica tests that were disabled by

[jira] [Commented] (HBASE-18352) Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614

[ https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203784#comment-16203784 ] huaxiang sun commented on HBASE-18352: -- Hi [~vrodionov], morning! I am also looking at this replica

<    5   6   7   8   9   10   11   12   13   14   >