[jira] [Commented] (HBASE-10679) Both clients get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId on the same region

[ https://issues.apache.org/jira/browse/HBASE-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925509#comment-13925509 ] Feng Honghua commented on HBASE-10679: -- I reran several times(5+) again locally and

[jira] [Created] (HBASE-10710) TestLogRolling.testLogRollOnDatanodeDeath fails occasionally in Hadoop QA run

Feng Honghua created HBASE-10710: Summary: TestLogRolling.testLogRollOnDatanodeDeath fails occasionally in Hadoop QA run Key: HBASE-10710 URL: https://issues.apache.org/jira/browse/HBASE-10710

[jira] [Commented] (HBASE-10679) Both clients get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId on the same region

[ https://issues.apache.org/jira/browse/HBASE-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925519#comment-13925519 ] Feng Honghua commented on HBASE-10679: -- HBASE-10710 is created for tracking failure

[jira] [Commented] (HBASE-10710) TestLogRolling.testLogRollOnDatanodeDeath fails occasionally in Hadoop QA run

[ https://issues.apache.org/jira/browse/HBASE-10710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925551#comment-13925551 ] Feng Honghua commented on HBASE-10710: -- I see...Thanks for the clarification,

[jira] [Commented] (HBASE-10710) TestLogRolling.testLogRollOnDatanodeDeath fails occasionally in Hadoop QA run

[ https://issues.apache.org/jira/browse/HBASE-10710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13925562#comment-13925562 ] Feng Honghua commented on HBASE-10710: -- Get your point, totally agree :-)

[jira] [Updated] (HBASE-10679) Both clients get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId on the same region

[ https://issues.apache.org/jira/browse/HBASE-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10679: - Attachment: HBASE-10679-trunk_v2.patch Both clients get wrong scan results if the first

[jira] [Commented] (HBASE-10651) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in Replication

[ https://issues.apache.org/jira/browse/HBASE-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924782#comment-13924782 ] Feng Honghua commented on HBASE-10651: -- Ping for review, thanks :-) Fix incorrect

[jira] [Commented] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924783#comment-13924783 ] Feng Honghua commented on HBASE-10595: -- Ping for review or further comment, [~enis]

[jira] [Updated] (HBASE-10662) RegionScanner is never closed if the region has been moved-out or re-opened when performing scan request

[ https://issues.apache.org/jira/browse/HBASE-10662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10662: - Attachment: HBASE-10662-0.96_v1.patch HBASE-10662-0.94_v1.patch [~lhofhansl] :

[jira] [Updated] (HBASE-10663) Some code cleanup of class Leases and ScannerListener.leaseExpired

[ https://issues.apache.org/jira/browse/HBASE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10663: - Summary: Some code cleanup of class Leases and ScannerListener.leaseExpired (was:

[jira] [Commented] (HBASE-10679) Both clients get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId on the same region

[ https://issues.apache.org/jira/browse/HBASE-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923687#comment-13923687 ] Feng Honghua commented on HBASE-10679: -- Would anybody help confirm the bug and

[jira] [Commented] (HBASE-10679) Both clients get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId on the same region

[ https://issues.apache.org/jira/browse/HBASE-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923790#comment-13923790 ] Feng Honghua commented on HBASE-10679: -- I reran the failed cases locally and they

[jira] [Commented] (HBASE-10679) Both clients get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId on the same region

[ https://issues.apache.org/jira/browse/HBASE-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924756#comment-13924756 ] Feng Honghua commented on HBASE-10679: -- bq.When the AtomicLong hits the max, it goes

[jira] [Updated] (HBASE-10679) Both clients operating on a same region will get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId

[ https://issues.apache.org/jira/browse/HBASE-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10679: - Status: Patch Available (was: Open) Both clients operating on a same region will get wrong

[jira] [Updated] (HBASE-10679) Both clients get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId on the same region

[ https://issues.apache.org/jira/browse/HBASE-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10679: - Summary: Both clients get wrong scan results if the first scanner expires and the second

[jira] [Created] (HBASE-10679) Both clients operating on a same region will get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId

Feng Honghua created HBASE-10679: Summary: Both clients operating on a same region will get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId Key: HBASE-10679

[jira] [Updated] (HBASE-10679) Both clients operating on a same region will get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId

[ https://issues.apache.org/jira/browse/HBASE-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10679: - Attachment: HBASE-10679-trunk_v1.patch Patch attached Both clients operating on a same region

[jira] [Updated] (HBASE-10662) RegionScanner never be closed if the region has been moved-out or re-opened when performing scan request

[ https://issues.apache.org/jira/browse/HBASE-10662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10662: - Summary: RegionScanner never be closed if the region has been moved-out or re-opened when

[jira] [Updated] (HBASE-10662) RegionScanner never be closed when the region has been moved-out or re-opened when performing scan request

[ https://issues.apache.org/jira/browse/HBASE-10662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10662: - Summary: RegionScanner never be closed when the region has been moved-out or re-opened when

[jira] [Updated] (HBASE-10679) Both clients operating on a same region will get wrong scan results if the first scanner expires and the second scanner is created with the same scannerId

[ https://issues.apache.org/jira/browse/HBASE-10679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10679: - Attachment: HBASE-10679-trunk_v2.patch Both clients operating on a same region will get wrong

[jira] [Created] (HBASE-10693) Correct declarations of Atomic* fields from 'volatile' to 'final'

Feng Honghua created HBASE-10693: Summary: Correct declarations of Atomic* fields from 'volatile' to 'final' Key: HBASE-10693 URL: https://issues.apache.org/jira/browse/HBASE-10693 Project: HBase

[jira] [Updated] (HBASE-10693) Correct declarations of Atomic* fields from 'volatile' to 'final'

[ https://issues.apache.org/jira/browse/HBASE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10693: - Attachment: HBASE-10693-trunk_v1.patch Patch attached Correct declarations of Atomic* fields

[jira] [Updated] (HBASE-10693) Correct declarations of Atomic* fields from 'volatile' to 'final'

[ https://issues.apache.org/jira/browse/HBASE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10693: - Description: By checking the usage of these Atomic* fields, they themselves don't change once

[jira] [Commented] (HBASE-10693) Correct declarations of Atomic* fields from 'volatile' to 'final'

[ https://issues.apache.org/jira/browse/HBASE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922055#comment-13922055 ] Feng Honghua commented on HBASE-10693: -- bq.Any other such cases in the code base?

[jira] [Updated] (HBASE-10693) Correct declarations of Atomic* fields from 'volatile' to 'final'

[ https://issues.apache.org/jira/browse/HBASE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10693: - Status: Patch Available (was: Open) Correct declarations of Atomic* fields from 'volatile' to

[jira] [Created] (HBASE-10662) RegionScanner should be closed and according lease should be cancelled in regionserver immediately if the related region has been re-opened during performing scan reques

Feng Honghua created HBASE-10662: Summary: RegionScanner should be closed and according lease should be cancelled in regionserver immediately if the related region has been re-opened during performing scan request Key:

[jira] [Updated] (HBASE-10662) RegionScanner should be closed and according lease should be cancelled in regionserver immediately if we find the related region has been re-opened during performing sca

[ https://issues.apache.org/jira/browse/HBASE-10662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10662: - Summary: RegionScanner should be closed and according lease should be cancelled in regionserver

[jira] [Updated] (HBASE-10662) RegionScanner should be closed and according lease should be cancelled in regionserver immediately if the related region has been re-opened during performing scan reques

[ https://issues.apache.org/jira/browse/HBASE-10662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10662: - Attachment: HBASE-10662-trunk_v1.patch Patch with an immediate fix attached Since no valid

[jira] [Commented] (HBASE-10662) RegionScanner should be closed and according lease should be cancelled in regionserver immediately if we find the related region has been re-opened during performing s

[ https://issues.apache.org/jira/browse/HBASE-10662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919208#comment-13919208 ] Feng Honghua commented on HBASE-10662: -- When we find the region has been re-opened

[jira] [Created] (HBASE-10663) Refactor/cleanup of class Leases and ScannerListener.leaseExpired

Feng Honghua created HBASE-10663: Summary: Refactor/cleanup of class Leases and ScannerListener.leaseExpired Key: HBASE-10663 URL: https://issues.apache.org/jira/browse/HBASE-10663 Project: HBase

[jira] [Updated] (HBASE-10663) Refactor/cleanup of class Leases and ScannerListener.leaseExpired

[ https://issues.apache.org/jira/browse/HBASE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10663: - Attachment: HBASE-10663-trunk_v1.patch Refactor/cleanup of class Leases and

[jira] [Commented] (HBASE-10662) RegionScanner should be closed and according lease should be cancelled in regionserver immediately if we find the related region has been re-opened during performing s

[ https://issues.apache.org/jira/browse/HBASE-10662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919331#comment-13919331 ] Feng Honghua commented on HBASE-10662: -- This bug occurs not only when regionserver

[jira] [Updated] (HBASE-10662) RegionScanner should be closed and according lease should be cancelled in regionserver immediately if we find the related region has been re-opened during performing sca

[ https://issues.apache.org/jira/browse/HBASE-10662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10662: - Description: During regionserver processes scan request from client, it fails the request by

[jira] [Updated] (HBASE-10651) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in Replication

[ https://issues.apache.org/jira/browse/HBASE-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10651: - Status: Patch Available (was: Open) Fix incorrect handling of IE that restores current

[jira] [Updated] (HBASE-10663) Refactor/cleanup of class Leases and ScannerListener.leaseExpired

[ https://issues.apache.org/jira/browse/HBASE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10663: - Status: Patch Available (was: Open) Refactor/cleanup of class Leases and

[jira] [Updated] (HBASE-10662) RegionScanner should be closed and according lease should be cancelled in regionserver immediately if we find the related region has been moved-out or re-opened during p

[ https://issues.apache.org/jira/browse/HBASE-10662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10662: - Summary: RegionScanner should be closed and according lease should be cancelled in regionserver

[jira] [Updated] (HBASE-10650) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in RegionServer

[ https://issues.apache.org/jira/browse/HBASE-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10650: - Status: Patch Available (was: Open) Thank [~nkeywal] for the prompt review! Fix incorrect

[jira] [Updated] (HBASE-10652) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in rpc

[ https://issues.apache.org/jira/browse/HBASE-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10652: - Status: Patch Available (was: Open) Thank [~nkeywal] and [~stack] for the prompt review! Fix

[jira] [Commented] (HBASE-10651) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in Replication

[ https://issues.apache.org/jira/browse/HBASE-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918865#comment-13918865 ] Feng Honghua commented on HBASE-10651: -- bq.How does going back to while to check if

[jira] [Updated] (HBASE-10651) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in Replication

[ https://issues.apache.org/jira/browse/HBASE-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10651: - Attachment: HBASE-10651-trunk_v2.patch New patch attached per [~stack]'s suggestion, Thanks.

[jira] [Commented] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918970#comment-13918970 ] Feng Honghua commented on HBASE-10595: -- Ping for further comment

[jira] [Commented] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917343#comment-13917343 ] Feng Honghua commented on HBASE-10595: -- Thanks [~v.himanshu] and [~enis] for review

[jira] [Commented] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917346#comment-13917346 ] Feng Honghua commented on HBASE-10595: -- bq.Lastly, what about we don't check the

[jira] [Commented] (HBASE-10649) TestMasterMetrics fails occasionally

[ https://issues.apache.org/jira/browse/HBASE-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917349#comment-13917349 ] Feng Honghua commented on HBASE-10649: -- [~yuzhih...@gmail.com] : I also encountered

[jira] [Updated] (HBASE-10629) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops

[ https://issues.apache.org/jira/browse/HBASE-10629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10629: - Component/s: (was: master) (was: Client) Fix incorrect handling of IE

[jira] [Created] (HBASE-10651) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in Replication

Feng Honghua created HBASE-10651: Summary: Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in Replication Key: HBASE-10651 URL:

[jira] [Created] (HBASE-10652) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in rpc

Feng Honghua created HBASE-10652: Summary: Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in rpc Key: HBASE-10652 URL:

[jira] [Created] (HBASE-10650) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in RegionServer

Feng Honghua created HBASE-10650: Summary: Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in RegionServer Key: HBASE-10650 URL:

[jira] [Updated] (HBASE-10650) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in RegionServer

[ https://issues.apache.org/jira/browse/HBASE-10650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10650: - Attachment: HBASE-10650-trunk_v1.patch patch attached Fix incorrect handling of IE that

[jira] [Updated] (HBASE-10651) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in Replication

[ https://issues.apache.org/jira/browse/HBASE-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10651: - Attachment: HBASE-10651-trunk_v1.patch patch attached Fix incorrect handling of IE that

[jira] [Updated] (HBASE-10652) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in rpc

[ https://issues.apache.org/jira/browse/HBASE-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10652: - Attachment: HBASE-10652-trunk_v1.patch patch attached Fix incorrect handling of IE that

[jira] [Commented] (HBASE-10651) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in Replication

[ https://issues.apache.org/jira/browse/HBASE-10651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917393#comment-13917393 ] Feng Honghua commented on HBASE-10651: -- # Directly go back to while() to check if

[jira] [Commented] (HBASE-10652) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops in rpc

[ https://issues.apache.org/jira/browse/HBASE-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917396#comment-13917396 ] Feng Honghua commented on HBASE-10652: -- Strictly speaking the previous

[jira] [Commented] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915541#comment-13915541 ] Feng Honghua commented on HBASE-10595: -- Thanks [~enis] for comment! sorry for the

[jira] [Updated] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10595: - Attachment: HBASE-10595-trunk_v4.patch HBaseAdmin.getTableDescriptor can wrongly get the

[jira] [Commented] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915909#comment-13915909 ] Feng Honghua commented on HBASE-10595: -- To align with listTables() for which table

[jira] [Created] (HBASE-10628) Fix semantic inconsistency among methods which are exposed to client

Feng Honghua created HBASE-10628: Summary: Fix semantic inconsistency among methods which are exposed to client Key: HBASE-10628 URL: https://issues.apache.org/jira/browse/HBASE-10628 Project: HBase

[jira] [Updated] (HBASE-10584) Inconsistency between tableExists and listTables in implementation

[ https://issues.apache.org/jira/browse/HBASE-10584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10584: - Issue Type: Sub-task (was: Bug) Parent: HBASE-10628 Inconsistency between tableExists

[jira] [Updated] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10595: - Issue Type: Sub-task (was: Bug) Parent: HBASE-10628 HBaseAdmin.getTableDescriptor can

[jira] [Created] (HBASE-10629) Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops

Feng Honghua created HBASE-10629: Summary: Fix incorrect handling of IE that restores current thread's interrupt status within while/for loops Key: HBASE-10629 URL:

[jira] [Resolved] (HBASE-9469) Synchronous replication

[ https://issues.apache.org/jira/browse/HBASE-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua resolved HBASE-9469. - Resolution: Won't Fix It has less value than expected as described in last comment Synchronous

[jira] [Commented] (HBASE-9469) Synchronous replication

[ https://issues.apache.org/jira/browse/HBASE-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915428#comment-13915428 ] Feng Honghua commented on HBASE-9469: - Thanks [~terry_zhang] for comment! bq.we need

[jira] [Created] (HBASE-10636) HBaseAdmin.deleteTable isn't 'really' synchronous in that still some cleanup in HMaster after client thinks deleteTable() succeeds

Feng Honghua created HBASE-10636: Summary: HBaseAdmin.deleteTable isn't 'really' synchronous in that still some cleanup in HMaster after client thinks deleteTable() succeeds Key: HBASE-10636 URL:

[jira] [Commented] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop to contact peer's zk ensemble and fails continuously

[ https://issues.apache.org/jira/browse/HBASE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910170#comment-13910170 ] Feng Honghua commented on HBASE-10575: -- [~lhofhansl], thanks for the review! :-)

[jira] [Updated] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10595: - Attachment: HBASE-10595-trunk_v3.patch HBaseAdmin.getTableDescriptor can wrongly get the

[jira] [Updated] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10595: - Attachment: HBASE-10595-trunk_v1.patch Patch attached A new unit test case is added to enforce

[jira] [Commented] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909715#comment-13909715 ] Feng Honghua commented on HBASE-10595: -- Additional note:

[jira] [Commented] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909716#comment-13909716 ] Feng Honghua commented on HBASE-10595: -- TestMasterObserver fails when I run 'mvn

[jira] [Commented] (HBASE-10584) Inconsistency between tableExists and listTables in implementation

[ https://issues.apache.org/jira/browse/HBASE-10584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909717#comment-13909717 ] Feng Honghua commented on HBASE-10584: -- I run 'mvn test' before attaching patch for

[jira] [Commented] (HBASE-10584) Inconsistency between tableExists and listTables in implementation

[ https://issues.apache.org/jira/browse/HBASE-10584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909722#comment-13909722 ] Feng Honghua commented on HBASE-10584: -- bq.We need a new issue after this one? There

[jira] [Commented] (HBASE-10556) Possible data loss due to non-handled DroppedSnapshotException for user-triggered flush from client/shell

[ https://issues.apache.org/jira/browse/HBASE-10556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909724#comment-13909724 ] Feng Honghua commented on HBASE-10556: -- Ping again...:-) Possible data loss due to

[jira] [Commented] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop to contact peer's zk ensemble and fails continuously

[ https://issues.apache.org/jira/browse/HBASE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909725#comment-13909725 ] Feng Honghua commented on HBASE-10575: -- Ping for another +1 for this jira to be

[jira] [Commented] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop to contact peer's zk ensemble and fails continuously

[ https://issues.apache.org/jira/browse/HBASE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910028#comment-13910028 ] Feng Honghua commented on HBASE-10575: -- bq.I would probably rename uninitialize to

[jira] [Commented] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop to contact peer's zk ensemble and fails continuously

[ https://issues.apache.org/jira/browse/HBASE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910041#comment-13910041 ] Feng Honghua commented on HBASE-10575: -- simply 'close', thanks...I meant 'close +

[jira] [Updated] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10595: - Attachment: HBASE-10595-trunk_v2.patch New patch 'fixing' previously failed TestMasterObserver

[jira] [Updated] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

[ https://issues.apache.org/jira/browse/HBASE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10595: - Status: Patch Available (was: Open) HBaseAdmin.getTableDescriptor can wrongly get the

[jira] [Commented] (HBASE-10584) Inconsistency between tableExists and listTables in implementation

[ https://issues.apache.org/jira/browse/HBASE-10584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909615#comment-13909615 ] Feng Honghua commented on HBASE-10584: -- I'm looking at the failed case.

[jira] [Created] (HBASE-10595) HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed

Feng Honghua created HBASE-10595: Summary: HBaseAdmin.getTableDescriptor can wrongly get the previous table's TableDescriptor even after the table dir in hdfs is removed Key: HBASE-10595 URL:

[jira] [Commented] (HBASE-10584) Inconsistency between tableExists and listTables in implementation

[ https://issues.apache.org/jira/browse/HBASE-10584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909669#comment-13909669 ] Feng Honghua commented on HBASE-10584: -- The failed case is due to another bug in

[jira] [Created] (HBASE-10584) Inconsistency between tableExists and listTables in implementation

Feng Honghua created HBASE-10584: Summary: Inconsistency between tableExists and listTables in implementation Key: HBASE-10584 URL: https://issues.apache.org/jira/browse/HBASE-10584 Project: HBase

[jira] [Updated] (HBASE-10584) Inconsistency between tableExists and listTables in implementation

[ https://issues.apache.org/jira/browse/HBASE-10584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10584: - Description: # HBaseAdmin.tableExists is implemented by scanning meta table #

[jira] [Commented] (HBASE-10516) Refactor code where Threads.sleep is called within a while/for loop

[ https://issues.apache.org/jira/browse/HBASE-10516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13908183#comment-13908183 ] Feng Honghua commented on HBASE-10516: -- [~nkeywal], thanks! :-) Refactor code

[jira] [Updated] (HBASE-10584) Inconsistency between tableExists and listTables in implementation

[ https://issues.apache.org/jira/browse/HBASE-10584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10584: - Attachment: HBASE-10584-trunk_v1.patch Inconsistency between tableExists and listTables in

[jira] [Created] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop and fails to contact peer's zk ensemble continuously

Feng Honghua created HBASE-10575: Summary: ReplicationSource thread can't be terminated if it runs into the loop and fails to contact peer's zk ensemble continuously Key: HBASE-10575 URL:

[jira] [Updated] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop and fails to contact peer's zk ensemble continuously

[ https://issues.apache.org/jira/browse/HBASE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10575: - Priority: Critical (was: Major) ReplicationSource thread can't be terminated if it runs into

[jira] [Updated] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop to contact peer's zk ensemble and fails continuously

[ https://issues.apache.org/jira/browse/HBASE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10575: - Summary: ReplicationSource thread can't be terminated if it runs into the loop to contact

[jira] [Updated] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop to contact peer's zk ensemble and fails continuously

[ https://issues.apache.org/jira/browse/HBASE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10575: - Attachment: HBASE-10575-trunk_v1.patch Patch attached for the fix And two minor changes # exit

[jira] [Commented] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop to contact peer's zk ensemble and fails continuously

[ https://issues.apache.org/jira/browse/HBASE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906766#comment-13906766 ] Feng Honghua commented on HBASE-10575: -- Looks like all branches have this same bug.

[jira] [Updated] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop to contact peer's zk ensemble and fails continuously

[ https://issues.apache.org/jira/browse/HBASE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10575: - Status: Patch Available (was: Open) ReplicationSource thread can't be terminated if it runs

[jira] [Commented] (HBASE-10575) ReplicationSource thread can't be terminated if it runs into the loop to contact peer's zk ensemble and fails continuously

[ https://issues.apache.org/jira/browse/HBASE-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906946#comment-13906946 ] Feng Honghua commented on HBASE-10575: -- unit tests pass in my local run, and the

[jira] [Commented] (HBASE-10497) Correct wrong handling and add proper handling for swallowed InterruptedException thrown by Thread.sleep under HBase-Client/HBase-Server folders systematically

[ https://issues.apache.org/jira/browse/HBASE-10497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907792#comment-13907792 ] Feng Honghua commented on HBASE-10497: -- Thank you [~nkeywal] :-) Correct wrong

[jira] [Commented] (HBASE-10516) Refactor code where Threads.sleep is called within a while/for loop

[ https://issues.apache.org/jira/browse/HBASE-10516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907837#comment-13907837 ] Feng Honghua commented on HBASE-10516: -- [~nkeywal], can this be committed as well?

[jira] [Updated] (HBASE-10516) Refactor code where Threads.sleep is called within a while/for loop

[ https://issues.apache.org/jira/browse/HBASE-10516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10516: - Attachment: HBASE-10516-trunk_v3.patch v3 patch attached per [~nkeywal]'s latest feedback on

[jira] [Commented] (HBASE-10516) Refactor code where Threads.sleep is called within a while/for loop

[ https://issues.apache.org/jira/browse/HBASE-10516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905077#comment-13905077 ] Feng Honghua commented on HBASE-10516: -- bq.Nice writeup @nkeywal (and nice

[jira] [Commented] (HBASE-10516) Refactor code where Threads.sleep is called within a while/for loop

[ https://issues.apache.org/jira/browse/HBASE-10516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905335#comment-13905335 ] Feng Honghua commented on HBASE-10516: -- bq.Sorry again the the review in 2 passes No

[jira] [Commented] (HBASE-10556) Possible data loss due to non-handled DroppedSnapshotException for user-triggered flush from client/shell

[ https://issues.apache.org/jira/browse/HBASE-10556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905351#comment-13905351 ] Feng Honghua commented on HBASE-10556: -- Thanks [~yuzhih...@gmail.com] for the

[jira] [Updated] (HBASE-10521) Add handling for swallowed InterruptedException thrown by Thread.sleep in RpcServer and RpcClient

[ https://issues.apache.org/jira/browse/HBASE-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10521: - Attachment: HBASE-10521-trunk_v3.patch v3 patch attached per [~nkeywal]'s latest review

[jira] [Commented] (HBASE-10524) Correct wrong handling and add proper handling for swallowed InterruptedException thrown by Thread.sleep in regionserver

[ https://issues.apache.org/jira/browse/HBASE-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905502#comment-13905502 ] Feng Honghua commented on HBASE-10524: -- Yes, both taskLoop and run handle

[jira] [Commented] (HBASE-10524) Correct wrong handling and add proper handling for swallowed InterruptedException thrown by Thread.sleep in regionserver

[ https://issues.apache.org/jira/browse/HBASE-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905509#comment-13905509 ] Feng Honghua commented on HBASE-10524: -- btw: the attached patch doesn't contain

[jira] [Commented] (HBASE-10521) Add handling for swallowed InterruptedException thrown by Thread.sleep in RpcServer and RpcClient

[ https://issues.apache.org/jira/browse/HBASE-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906538#comment-13906538 ] Feng Honghua commented on HBASE-10521: -- I also rerun the unit tests and all pass

  1   2   3   4   5   6   >