[jira] [Assigned] (PHOENIX-5971) Triple performance reduction of delete operation from 4.4.0 Upgrade to 4.13.1

2020-06-21 Thread Chao Wang (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chao Wang reassigned PHOENIX-5971:
--

Assignee: Chao Wang

> Triple performance reduction of delete operation from 4.4.0 Upgrade to 4.13.1
> -
>
> Key: PHOENIX-5971
> URL: https://issues.apache.org/jira/browse/PHOENIX-5971
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.13.1
> Environment: 200+ node
>Reporter: Chao Wang
>Assignee: Chao Wang
>Priority: Major
>
> phoenix from 4.4.0 Upgrade to 4.13.1 in my environmental, delete operation 
> triple performance reduction. for example a sql (delete  ...  from ...) will 
> delete million of data, and then hundreds of concurrent. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5971) Triple performance reduction of delete operation from 4.4.0 Upgrade to 4.13.1

2020-06-21 Thread Chao Wang (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chao Wang updated PHOENIX-5971:
---
Environment: 200+ node

> Triple performance reduction of delete operation from 4.4.0 Upgrade to 4.13.1
> -
>
> Key: PHOENIX-5971
> URL: https://issues.apache.org/jira/browse/PHOENIX-5971
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.13.1
> Environment: 200+ node
>Reporter: Chao Wang
>Priority: Major
>
> phoenix from 4.4.0 Upgrade to 4.13.1 in my environmental, delete operation 
> triple performance reduction. for example a sql (delete  ...  from ...) will 
> delete million of data, and then hundreds of concurrent. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (PHOENIX-5971) Triple performance reduction of delete operation from 4.4.0 Upgrade to 4.13.1

2020-06-21 Thread Chao Wang (Jira) 
Chao Wang created PHOENIX-5971:
--

 Summary: Triple performance reduction of delete operation from 
4.4.0 Upgrade to 4.13.1
 Key: PHOENIX-5971
 URL: https://issues.apache.org/jira/browse/PHOENIX-5971
 Project: Phoenix
  Issue Type: Bug
  Components: core
Affects Versions: 4.13.1
Reporter: Chao Wang


phoenix from 4.4.0 Upgrade to 4.13.1 in my environmental, delete operation 
triple performance reduction. for example a sql (delete  ...  from ...) will 
delete million of data, and then hundreds of concurrent. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests hange

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5970:
--
Description: 
After PHOENIX-5962, the ITtests still hange , I noticed the RegionServer is 
blocked as follows : (by 4.x branch and HBase1.4.10) :
{code:java}
Thread 31512: (state = BLOCKED)
 - java.lang.Thread.sleep(long) @bci=0 (Compiled frame; information may be 
imprecise)
 - java.lang.Thread.sleep(long, int) @bci=57, line=340 (Compiled frame)
 - java.util.concurrent.TimeUnit.sleep(long) @bci=23, line=386 (Compiled frame)
 - org.apache.hadoop.hbase.util.RetryCounter.sleepUntilNextRetry() @bci=110, 
line=158 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(java.lang.String,
 org.apache.zookeeper.Watcher, org.apache.zookeeper.data.Stat) @bci=180, 
line=367 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.ZKUtil.getData(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 java.lang.String) @bci=11, line=629 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionState(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int) @bci=23, line=487 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionLocation(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int) @bci=6, line=168 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int, long) @bci=63, line=607 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 long) @bci=9, line=588 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 long, org.apache.hadoop.conf.Configuration) @bci=34, line=561 (Compiled frame)
 - org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation() 
@bci=94, line=61 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateMeta(org.apache.hadoop.hbase.TableName,
 boolean, int) @bci=205, line=1266 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=119, line=1227 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.relocateRegion(org.apache.hadoop.hbase.TableName,
 byte[], int) @bci=93, line=1201 (Interpreted frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.relocateRegion(org.apache.hadoop.hbase.TableName,
 byte[], int) @bci=9, line=41 (Interpreted frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=1668, line=1419 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=138, line=1230 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(boolean,
 int, org.apache.hadoop.hbase.client.ClusterConnection, 
org.apache.hadoop.hbase.TableName, byte[]) @bci=22, line=356 (Compiled frame)
 - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) 
@bci=164, line=153 (Compiled frame)
 - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) @bci=6, 
line=58 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(org.apache.hadoop.hbase.client.RetryingCallable,
 int) @bci=30, line=219 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ClientScanner.call(org.apache.hadoop.hbase.client.ScannerCallableWithReplicas,
 org.apache.hadoop.hbase.client.RpcRetryingCaller, int, boolean) @bci=34, 
line=275 (Compiled frame)
 - org.apache.hadoop.hbase.client.ClientScanner.loadCache() @bci=109, line=436 
(Compiled frame)
 - org.apache.hadoop.hbase.client.ClientScanner.next() @bci=68, line=310 
(Compiled frame)
 - 
org.apache.phoenix.util.ViewUtil.findRelatedViews(org.apache.hadoop.hbase.client.Table,
 byte[], byte[], byte[], org.apache.phoenix.schema.PTable$LinkType, long) 
@bci=281, line=126 (Compiled frame)
 - 
org.apache.phoenix.util.ViewUtil.dropChildViews(org.apache.hadoop.hbase.coprocessor.RegionCoprocessorEnvironment,
 byte[], byte[], byte[], byte[]) @bci=62, line=198 (Compiled frame)
 - 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.createTable(com.

Re: No builds on Phoenix-Master jenkins since Feb 19th?

2020-06-21 Thread cheng...@apache.org 












I observed that when the ITtests hange,  the ZK connection exhaustion is caused 
by ViewUtil.dropChildViews , and I opened a JIRA PHOENIX-5970 to solve it, 
seems that it works.





At 2020-06-19 14:58:27, "Istvan Toth"  wrote:
>The hanging test suite issue has been fixed by Richard Antal's PHOENIX-5962
> .
>Tests should be back to normal (that is, they're still flakey as fresh snow)
>
>Rajeshbabu, is there an easy way (specific message in the logs) for
>identifying the ZK connection exhaustion situation?
>
>Istvan
>
>On Thu, Jun 18, 2020 at 2:49 AM rajeshb...@apache.org <
>chrajeshbab...@gmail.com> wrote:
>
>> Just my observation related tests hang or flaky ness is that when there are
>> connections created which involves zookeeper connection then at some point
>> of time zookeeper sees too many connections and not allow to create further
>> connections then the cluster won't be terminated immediately and tests
>> hangs. We can identify such cases and close the connections properly if
>> any.
>>
>> Thanks,
>> Rajeshbabu.
>>
>> On Tue, Jun 16, 2020, 12:12 PM Istvan Toth  wrote:
>>
>> > What we really need is getting our test suite (and infra) sorted out.
>> > Your suggestions are already part of the process, it's just that lately
>> > everyone ignores them, because the precommit tests have been next to
>> > useless for a good while.
>> >
>> > I think that if developers can be reasonably sure that the precommit
>> > failure that they see is not some kind of random/known flake, they (we)
>> > will take them seriously, and not commit until they(we) get it right.
>> >
>> > Blocking further commits until the tests are fixed is one drastic, but
>> > possibly necessary measure to achieve this.
>> > And once we get them fixed, we will indeed need to be more vigilant in
>> not
>> > letting the situation deteriorate.
>> >
>> > Istvan
>> >
>> > On Mon, Jun 15, 2020 at 7:30 PM Andrew Purtell 
>> > wrote:
>> >
>> > > So it's time to enforce an automatic revert if build fails policy?
>> > > Ideally, no commit before a precommit passes.
>> > > If that fails, if someone discovers failing tests and can git bisect to
>> > the
>> > > cause, automatic revert of the offending commit.
>> > >
>> > > YDYT?
>> > >
>> > >
>> > > On Sun, Jun 14, 2020 at 10:20 PM Istvan Toth
>> > > >
>> > > wrote:
>> > >
>> > > > Unfortunately you are not missing anything, Lars :(
>> > > >
>> > > > What's worse, the tests are not only failing, they even hang since
>> Jun
>> > 2.
>> > > > Master is in a similar state.
>> > > >
>> > > > regards
>> > > > Istvan
>> > > >
>> > > > On Sun, Jun 14, 2020 at 12:03 AM la...@apache.org 
>> > > > wrote:
>> > > >
>> > > > > Thanks Istvan.
>> > > > >
>> > > > > Just checked the builds. Looks like the 4.x builds have not passed
>> a
>> > > > > single time since May 20th.
>> > > > >
>> > > > > I hope I am missing something... Otherwise this would be pretty
>> > > > > frustrating. :)
>> > > > > (Since pleading doesn't appear to help, maybe we should
>> automatically
>> > > > > block all commits until all tests pass...?)
>> > > > >
>> > > > > -- Lars
>> > > > >
>> > > > >
>> > > > > On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <
>> > > > st...@apache.org>
>> > > > > wrote:
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > I've deleted all but the four Phoenix jobs listed in the JIRA.
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > *István Tóth* | Staff Software Engineer
>> > > > st...@cloudera.com 
>> > > > [image: Cloudera] 
>> > > > [image: Cloudera on Twitter]  [image:
>> > > > Cloudera on Facebook]  [image:
>> > > Cloudera
>> > > > on LinkedIn] 
>> > > > 
>> > > > --
>> > > >
>> > >
>> > >
>> > > --
>> > > Best regards,
>> > > Andrew
>> > >
>> > > Words like orphans lost among the crosstalk, meaning torn from truth's
>> > > decrepit hands
>> > >- A23, Crosstalk
>> > >
>> >
>>

Re: No builds on Phoenix-Master jenkins since Feb 19th?

2020-06-21 Thread 程磊 












I observed that when the ITtests hange,  the ZK connection exhaustion is caused 
by ViewUtil.dropChildViews , and I opened a JIRA PHOENIX-5970 to solve it, 
seems that it works.





At 2020-06-19 14:58:27, "Istvan Toth"  wrote:
>The hanging test suite issue has been fixed by Richard Antal's PHOENIX-5962
> .
>Tests should be back to normal (that is, they're still flakey as fresh snow)
>
>Rajeshbabu, is there an easy way (specific message in the logs) for
>identifying the ZK connection exhaustion situation?
>
>Istvan
>
>On Thu, Jun 18, 2020 at 2:49 AM rajeshb...@apache.org <
>chrajeshbab...@gmail.com> wrote:
>
>> Just my observation related tests hang or flaky ness is that when there are
>> connections created which involves zookeeper connection then at some point
>> of time zookeeper sees too many connections and not allow to create further
>> connections then the cluster won't be terminated immediately and tests
>> hangs. We can identify such cases and close the connections properly if
>> any.
>>
>> Thanks,
>> Rajeshbabu.
>>
>> On Tue, Jun 16, 2020, 12:12 PM Istvan Toth  wrote:
>>
>> > What we really need is getting our test suite (and infra) sorted out.
>> > Your suggestions are already part of the process, it's just that lately
>> > everyone ignores them, because the precommit tests have been next to
>> > useless for a good while.
>> >
>> > I think that if developers can be reasonably sure that the precommit
>> > failure that they see is not some kind of random/known flake, they (we)
>> > will take them seriously, and not commit until they(we) get it right.
>> >
>> > Blocking further commits until the tests are fixed is one drastic, but
>> > possibly necessary measure to achieve this.
>> > And once we get them fixed, we will indeed need to be more vigilant in
>> not
>> > letting the situation deteriorate.
>> >
>> > Istvan
>> >
>> > On Mon, Jun 15, 2020 at 7:30 PM Andrew Purtell 
>> > wrote:
>> >
>> > > So it's time to enforce an automatic revert if build fails policy?
>> > > Ideally, no commit before a precommit passes.
>> > > If that fails, if someone discovers failing tests and can git bisect to
>> > the
>> > > cause, automatic revert of the offending commit.
>> > >
>> > > YDYT?
>> > >
>> > >
>> > > On Sun, Jun 14, 2020 at 10:20 PM Istvan Toth
>> > > >
>> > > wrote:
>> > >
>> > > > Unfortunately you are not missing anything, Lars :(
>> > > >
>> > > > What's worse, the tests are not only failing, they even hang since
>> Jun
>> > 2.
>> > > > Master is in a similar state.
>> > > >
>> > > > regards
>> > > > Istvan
>> > > >
>> > > > On Sun, Jun 14, 2020 at 12:03 AM la...@apache.org 
>> > > > wrote:
>> > > >
>> > > > > Thanks Istvan.
>> > > > >
>> > > > > Just checked the builds. Looks like the 4.x builds have not passed
>> a
>> > > > > single time since May 20th.
>> > > > >
>> > > > > I hope I am missing something... Otherwise this would be pretty
>> > > > > frustrating. :)
>> > > > > (Since pleading doesn't appear to help, maybe we should
>> automatically
>> > > > > block all commits until all tests pass...?)
>> > > > >
>> > > > > -- Lars
>> > > > >
>> > > > >
>> > > > > On Tuesday, April 21, 2020, 5:33:52 AM PDT, Istvan Toth <
>> > > > st...@apache.org>
>> > > > > wrote:
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > I've deleted all but the four Phoenix jobs listed in the JIRA.
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > *István Tóth* | Staff Software Engineer
>> > > > st...@cloudera.com 
>> > > > [image: Cloudera] 
>> > > > [image: Cloudera on Twitter]  [image:
>> > > > Cloudera on Facebook]  [image:
>> > > Cloudera
>> > > > on LinkedIn] 
>> > > > 
>> > > > --
>> > > >
>> > >
>> > >
>> > > --
>> > > Best regards,
>> > > Andrew
>> > >
>> > > Words like orphans lost among the crosstalk, meaning torn from truth's
>> > > decrepit hands
>> > >- A23, Crosstalk
>> > >
>> >
>>

[jira] [Resolved] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests hange

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei resolved PHOENIX-5970.
---
Resolution: Fixed

> ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests 
> hange
> 
>
> Key: PHOENIX-5970
> URL: https://issues.apache.org/jira/browse/PHOENIX-5970
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: chenglei
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5970_v1-4.x.patch
>
>
> When ITtests hange recently , I noticed the RegionServer is blocked as 
> follows : (for 4.x branch and HBase1.4.10) :
> {code:java}
> Thread 31512: (state = BLOCKED)
>  - java.lang.Thread.sleep(long) @bci=0 (Compiled frame; information may be 
> imprecise)
>  - java.lang.Thread.sleep(long, int) @bci=57, line=340 (Compiled frame)
>  - java.util.concurrent.TimeUnit.sleep(long) @bci=23, line=386 (Compiled 
> frame)
>  - org.apache.hadoop.hbase.util.RetryCounter.sleepUntilNextRetry() @bci=110, 
> line=158 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(java.lang.String,
>  org.apache.zookeeper.Watcher, org.apache.zookeeper.data.Stat) @bci=180, 
> line=367 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.ZKUtil.getData(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  java.lang.String) @bci=11, line=629 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionState(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  int) @bci=23, line=487 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionLocation(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  int) @bci=6, line=168 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  int, long) @bci=63, line=607 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  long) @bci=9, line=588 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  long, org.apache.hadoop.conf.Configuration) @bci=34, line=561 (Compiled 
> frame)
>  - org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation() 
> @bci=94, line=61 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateMeta(org.apache.hadoop.hbase.TableName,
>  boolean, int) @bci=205, line=1266 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=119, line=1227 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.relocateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], int) @bci=93, line=1201 (Interpreted frame)
>  - 
> org.apache.hadoop.hbase.client.CoprocessorHConnection.relocateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], int) @bci=9, line=41 (Interpreted frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=1668, line=1419 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=138, line=1230 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(boolean,
>  int, org.apache.hadoop.hbase.client.ClusterConnection, 
> org.apache.hadoop.hbase.TableName, byte[]) @bci=22, line=356 (Compiled frame)
>  - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) 
> @bci=164, line=153 (Compiled frame)
>  - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) 
> @bci=6, line=58 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(org.apache.hadoop.hbase.client.RetryingCallable,
>  int) @bci=30, line=219 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ClientScanner.call(org.apache.hadoop.hbase.client.ScannerCallableWithReplicas,
>  org.apache.hadoop.hbase.client.RpcRetryingCaller, int, boolean) @bci=34, 
> line=275

[jira] [Assigned] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests hange

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei reassigned PHOENIX-5970:
-

Assignee: chenglei

> ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests 
> hange
> 
>
> Key: PHOENIX-5970
> URL: https://issues.apache.org/jira/browse/PHOENIX-5970
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: chenglei
>Assignee: chenglei
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5970_v1-4.x.patch
>
>
> When ITtests hange recently , I noticed the RegionServer is blocked as 
> follows : (for 4.x branch and HBase1.4.10) :
> {code:java}
> Thread 31512: (state = BLOCKED)
>  - java.lang.Thread.sleep(long) @bci=0 (Compiled frame; information may be 
> imprecise)
>  - java.lang.Thread.sleep(long, int) @bci=57, line=340 (Compiled frame)
>  - java.util.concurrent.TimeUnit.sleep(long) @bci=23, line=386 (Compiled 
> frame)
>  - org.apache.hadoop.hbase.util.RetryCounter.sleepUntilNextRetry() @bci=110, 
> line=158 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(java.lang.String,
>  org.apache.zookeeper.Watcher, org.apache.zookeeper.data.Stat) @bci=180, 
> line=367 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.ZKUtil.getData(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  java.lang.String) @bci=11, line=629 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionState(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  int) @bci=23, line=487 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionLocation(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  int) @bci=6, line=168 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  int, long) @bci=63, line=607 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  long) @bci=9, line=588 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  long, org.apache.hadoop.conf.Configuration) @bci=34, line=561 (Compiled 
> frame)
>  - org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation() 
> @bci=94, line=61 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateMeta(org.apache.hadoop.hbase.TableName,
>  boolean, int) @bci=205, line=1266 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=119, line=1227 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.relocateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], int) @bci=93, line=1201 (Interpreted frame)
>  - 
> org.apache.hadoop.hbase.client.CoprocessorHConnection.relocateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], int) @bci=9, line=41 (Interpreted frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=1668, line=1419 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=138, line=1230 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(boolean,
>  int, org.apache.hadoop.hbase.client.ClusterConnection, 
> org.apache.hadoop.hbase.TableName, byte[]) @bci=22, line=356 (Compiled frame)
>  - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) 
> @bci=164, line=153 (Compiled frame)
>  - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) 
> @bci=6, line=58 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(org.apache.hadoop.hbase.client.RetryingCallable,
>  int) @bci=30, line=219 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ClientScanner.call(org.apache.hadoop.hbase.client.ScannerCallableWithReplicas,
>  org.apache.hadoop.hbase.client.RpcRetryingCalle

[jira] [Updated] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests hange

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5970:
--
Fix Version/s: 4.16.0
   5.1.0

> ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests 
> hange
> 
>
> Key: PHOENIX-5970
> URL: https://issues.apache.org/jira/browse/PHOENIX-5970
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: chenglei
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5970_v1-4.x.patch
>
>
> When ITtests hange recently , I noticed the RegionServer is blocked as 
> follows : (for 4.x branch and HBase1.4.10) :
> {code:java}
> Thread 31512: (state = BLOCKED)
>  - java.lang.Thread.sleep(long) @bci=0 (Compiled frame; information may be 
> imprecise)
>  - java.lang.Thread.sleep(long, int) @bci=57, line=340 (Compiled frame)
>  - java.util.concurrent.TimeUnit.sleep(long) @bci=23, line=386 (Compiled 
> frame)
>  - org.apache.hadoop.hbase.util.RetryCounter.sleepUntilNextRetry() @bci=110, 
> line=158 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(java.lang.String,
>  org.apache.zookeeper.Watcher, org.apache.zookeeper.data.Stat) @bci=180, 
> line=367 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.ZKUtil.getData(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  java.lang.String) @bci=11, line=629 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionState(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  int) @bci=23, line=487 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionLocation(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  int) @bci=6, line=168 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  int, long) @bci=63, line=607 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  long) @bci=9, line=588 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
>  long, org.apache.hadoop.conf.Configuration) @bci=34, line=561 (Compiled 
> frame)
>  - org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation() 
> @bci=94, line=61 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateMeta(org.apache.hadoop.hbase.TableName,
>  boolean, int) @bci=205, line=1266 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=119, line=1227 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.relocateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], int) @bci=93, line=1201 (Interpreted frame)
>  - 
> org.apache.hadoop.hbase.client.CoprocessorHConnection.relocateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], int) @bci=9, line=41 (Interpreted frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=1668, line=1419 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=138, line=1230 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
>  byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(boolean,
>  int, org.apache.hadoop.hbase.client.ClusterConnection, 
> org.apache.hadoop.hbase.TableName, byte[]) @bci=22, line=356 (Compiled frame)
>  - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) 
> @bci=164, line=153 (Compiled frame)
>  - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) 
> @bci=6, line=58 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(org.apache.hadoop.hbase.client.RetryingCallable,
>  int) @bci=30, line=219 (Compiled frame)
>  - 
> org.apache.hadoop.hbase.client.ClientScanner.call(org.apache.hadoop.hbase.client.ScannerCallableWithReplicas,
>  org.apache.hadoop.hbase.client.RpcRetryingCaller, int, boo

[jira] [Updated] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests hange

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5970:
--
Description: 
When ITtests hange recently , I noticed the RegionServer is blocked as follows 
: (for 4.x branch and HBase1.4.10) :
{code:java}
Thread 31512: (state = BLOCKED)
 - java.lang.Thread.sleep(long) @bci=0 (Compiled frame; information may be 
imprecise)
 - java.lang.Thread.sleep(long, int) @bci=57, line=340 (Compiled frame)
 - java.util.concurrent.TimeUnit.sleep(long) @bci=23, line=386 (Compiled frame)
 - org.apache.hadoop.hbase.util.RetryCounter.sleepUntilNextRetry() @bci=110, 
line=158 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(java.lang.String,
 org.apache.zookeeper.Watcher, org.apache.zookeeper.data.Stat) @bci=180, 
line=367 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.ZKUtil.getData(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 java.lang.String) @bci=11, line=629 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionState(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int) @bci=23, line=487 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionLocation(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int) @bci=6, line=168 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int, long) @bci=63, line=607 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 long) @bci=9, line=588 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 long, org.apache.hadoop.conf.Configuration) @bci=34, line=561 (Compiled frame)
 - org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation() 
@bci=94, line=61 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateMeta(org.apache.hadoop.hbase.TableName,
 boolean, int) @bci=205, line=1266 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=119, line=1227 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.relocateRegion(org.apache.hadoop.hbase.TableName,
 byte[], int) @bci=93, line=1201 (Interpreted frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.relocateRegion(org.apache.hadoop.hbase.TableName,
 byte[], int) @bci=9, line=41 (Interpreted frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=1668, line=1419 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=138, line=1230 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(boolean,
 int, org.apache.hadoop.hbase.client.ClusterConnection, 
org.apache.hadoop.hbase.TableName, byte[]) @bci=22, line=356 (Compiled frame)
 - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) 
@bci=164, line=153 (Compiled frame)
 - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) @bci=6, 
line=58 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(org.apache.hadoop.hbase.client.RetryingCallable,
 int) @bci=30, line=219 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ClientScanner.call(org.apache.hadoop.hbase.client.ScannerCallableWithReplicas,
 org.apache.hadoop.hbase.client.RpcRetryingCaller, int, boolean) @bci=34, 
line=275 (Compiled frame)
 - org.apache.hadoop.hbase.client.ClientScanner.loadCache() @bci=109, line=436 
(Compiled frame)
 - org.apache.hadoop.hbase.client.ClientScanner.next() @bci=68, line=310 
(Compiled frame)
 - 
org.apache.phoenix.util.ViewUtil.findRelatedViews(org.apache.hadoop.hbase.client.Table,
 byte[], byte[], byte[], org.apache.phoenix.schema.PTable$LinkType, long) 
@bci=281, line=126 (Compiled frame)
 - 
org.apache.phoenix.util.ViewUtil.dropChildViews(org.apache.hadoop.hbase.coprocessor.RegionCoprocessorEnvironment,
 byte[], byte[], byte[], byte[]) @bci=62, line=198 (Compiled frame)
 - 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.createTable(com.google.protobuf

[jira] [Updated] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests hange

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5970:
--
Description: 
When ITtests hange recently , I noticed the RegionServer is blocked as follows 
: (for 4.x branch and HBase1.4.10) :
{code:java}
Thread 31512: (state = BLOCKED)
 - java.lang.Thread.sleep(long) @bci=0 (Compiled frame; information may be 
imprecise)
 - java.lang.Thread.sleep(long, int) @bci=57, line=340 (Compiled frame)
 - java.util.concurrent.TimeUnit.sleep(long) @bci=23, line=386 (Compiled frame)
 - org.apache.hadoop.hbase.util.RetryCounter.sleepUntilNextRetry() @bci=110, 
line=158 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(java.lang.String,
 org.apache.zookeeper.Watcher, org.apache.zookeeper.data.Stat) @bci=180, 
line=367 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.ZKUtil.getData(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 java.lang.String) @bci=11, line=629 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionState(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int) @bci=23, line=487 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionLocation(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int) @bci=6, line=168 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int, long) @bci=63, line=607 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 long) @bci=9, line=588 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 long, org.apache.hadoop.conf.Configuration) @bci=34, line=561 (Compiled frame)
 - org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation() 
@bci=94, line=61 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateMeta(org.apache.hadoop.hbase.TableName,
 boolean, int) @bci=205, line=1266 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=119, line=1227 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.relocateRegion(org.apache.hadoop.hbase.TableName,
 byte[], int) @bci=93, line=1201 (Interpreted frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.relocateRegion(org.apache.hadoop.hbase.TableName,
 byte[], int) @bci=9, line=41 (Interpreted frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=1668, line=1419 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=138, line=1230 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(boolean,
 int, org.apache.hadoop.hbase.client.ClusterConnection, 
org.apache.hadoop.hbase.TableName, byte[]) @bci=22, line=356 (Compiled frame)
 - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) 
@bci=164, line=153 (Compiled frame)
 - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) @bci=6, 
line=58 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(org.apache.hadoop.hbase.client.RetryingCallable,
 int) @bci=30, line=219 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ClientScanner.call(org.apache.hadoop.hbase.client.ScannerCallableWithReplicas,
 org.apache.hadoop.hbase.client.RpcRetryingCaller, int, boolean) @bci=34, 
line=275 (Compiled frame)
 - org.apache.hadoop.hbase.client.ClientScanner.loadCache() @bci=109, line=436 
(Compiled frame)
 - org.apache.hadoop.hbase.client.ClientScanner.next() @bci=68, line=310 
(Compiled frame)
 - 
org.apache.phoenix.util.ViewUtil.findRelatedViews(org.apache.hadoop.hbase.client.Table,
 byte[], byte[], byte[], org.apache.phoenix.schema.PTable$LinkType, long) 
@bci=281, line=126 (Compiled frame)
 - 
org.apache.phoenix.util.ViewUtil.dropChildViews(org.apache.hadoop.hbase.coprocessor.RegionCoprocessorEnvironment,
 byte[], byte[], byte[], byte[]) @bci=62, line=198 (Compiled frame)
 - 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.createTable(com.google.protobuf

[jira] [Updated] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests hange

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5970:
--
Description: 
When ITtests hange recently , I noticed the RegionServer is blocked as follows 
: (for 4.x branch and HBase1.4.10) :
{code:java}
Thread 31512: (state = BLOCKED)
 - java.lang.Thread.sleep(long) @bci=0 (Compiled frame; information may be 
imprecise)
 - java.lang.Thread.sleep(long, int) @bci=57, line=340 (Compiled frame)
 - java.util.concurrent.TimeUnit.sleep(long) @bci=23, line=386 (Compiled frame)
 - org.apache.hadoop.hbase.util.RetryCounter.sleepUntilNextRetry() @bci=110, 
line=158 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(java.lang.String,
 org.apache.zookeeper.Watcher, org.apache.zookeeper.data.Stat) @bci=180, 
line=367 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.ZKUtil.getData(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 java.lang.String) @bci=11, line=629 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionState(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int) @bci=23, line=487 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionLocation(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int) @bci=6, line=168 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 int, long) @bci=63, line=607 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 long) @bci=9, line=588 (Compiled frame)
 - 
org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher,
 long, org.apache.hadoop.conf.Configuration) @bci=34, line=561 (Compiled frame)
 - org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation() 
@bci=94, line=61 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateMeta(org.apache.hadoop.hbase.TableName,
 boolean, int) @bci=205, line=1266 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=119, line=1227 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.relocateRegion(org.apache.hadoop.hbase.TableName,
 byte[], int) @bci=93, line=1201 (Interpreted frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.relocateRegion(org.apache.hadoop.hbase.TableName,
 byte[], int) @bci=9, line=41 (Interpreted frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=1668, line=1419 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=138, line=1230 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(org.apache.hadoop.hbase.TableName,
 byte[], boolean, boolean, int) @bci=13, line=41 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(boolean,
 int, org.apache.hadoop.hbase.client.ClusterConnection, 
org.apache.hadoop.hbase.TableName, byte[]) @bci=22, line=356 (Compiled frame)
 - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) 
@bci=164, line=153 (Compiled frame)
 - org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(int) @bci=6, 
line=58 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(org.apache.hadoop.hbase.client.RetryingCallable,
 int) @bci=30, line=219 (Compiled frame)
 - 
org.apache.hadoop.hbase.client.ClientScanner.call(org.apache.hadoop.hbase.client.ScannerCallableWithReplicas,
 org.apache.hadoop.hbase.client.RpcRetryingCaller, int, boolean) @bci=34, 
line=275 (Compiled frame)
 - org.apache.hadoop.hbase.client.ClientScanner.loadCache() @bci=109, line=436 
(Compiled frame)
 - org.apache.hadoop.hbase.client.ClientScanner.next() @bci=68, line=310 
(Compiled frame)
 - 
org.apache.phoenix.util.ViewUtil.findRelatedViews(org.apache.hadoop.hbase.client.Table,
 byte[], byte[], byte[], org.apache.phoenix.schema.PTable$LinkType, long) 
@bci=281, line=126 (Compiled frame)
 - 
org.apache.phoenix.util.ViewUtil.dropChildViews(org.apache.hadoop.hbase.coprocessor.RegionCoprocessorEnvironment,
 byte[], byte[], byte[], byte[]) @bci=62, line=198 (Compiled frame)
 - 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.createTable(com.google.protobuf

[jira] [Updated] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests hange

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5970:
--
Summary: ViewUtil.dropChildViews may cause HConnection leak which may cause 
ITtests hange  (was: ViewUtil.dropChildViews may cause HConnection leak)

> ViewUtil.dropChildViews may cause HConnection leak which may cause ITtests 
> hange
> 
>
> Key: PHOENIX-5970
> URL: https://issues.apache.org/jira/browse/PHOENIX-5970
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: chenglei
>Priority: Major
> Attachments: PHOENIX-5970_v1-4.x.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5970:
--
Attachment: PHOENIX-5970_v1-4.x.patch

> ViewUtil.dropChildViews may cause HConnection leak
> --
>
> Key: PHOENIX-5970
> URL: https://issues.apache.org/jira/browse/PHOENIX-5970
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: chenglei
>Priority: Major
> Attachments: PHOENIX-5970_v1-4.x.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5970:
--
Attachment: (was: PHOENIX-5970_v1-4.x.patch)

> ViewUtil.dropChildViews may cause HConnection leak
> --
>
> Key: PHOENIX-5970
> URL: https://issues.apache.org/jira/browse/PHOENIX-5970
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: chenglei
>Priority: Major
> Attachments: PHOENIX-5970_v1-4.x.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5970:
--
Attachment: PHOENIX-5970_v1-4.x.patch

> ViewUtil.dropChildViews may cause HConnection leak
> --
>
> Key: PHOENIX-5970
> URL: https://issues.apache.org/jira/browse/PHOENIX-5970
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: chenglei
>Priority: Major
> Attachments: PHOENIX-5970_v1-4.x.patch
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (PHOENIX-5970) org.apache.phoenix.util.ViewUtil.dropChildViews may cause HConnection leak

2020-06-21 Thread chenglei (Jira) 
chenglei created PHOENIX-5970:
-

 Summary: org.apache.phoenix.util.ViewUtil.dropChildViews may cause 
HConnection leak
 Key: PHOENIX-5970
 URL: https://issues.apache.org/jira/browse/PHOENIX-5970
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.15.0
Reporter: chenglei






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5970) ViewUtil.dropChildViews may cause HConnection leak

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5970:
--
Summary: ViewUtil.dropChildViews may cause HConnection leak  (was: 
org.apache.phoenix.util.ViewUtil.dropChildViews may cause HConnection leak)

> ViewUtil.dropChildViews may cause HConnection leak
> --
>
> Key: PHOENIX-5970
> URL: https://issues.apache.org/jira/browse/PHOENIX-5970
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.15.0
>Reporter: chenglei
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5897) SingleKeyValueTuple.toString() returns unexpected result

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5897:
--
Fix Version/s: 4.16.0

> SingleKeyValueTuple.toString() returns unexpected result
> 
>
> Key: PHOENIX-5897
> URL: https://issues.apache.org/jira/browse/PHOENIX-5897
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 5.0.0-alpha
>Reporter: Chen Feng
>Assignee: Chen Feng
>Priority: Minor
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5897-v1.patch, PHOENIX-5897_v1-4.x.patch
>
>
> In SingleKeyValueTuple.toString(), the code is shown as follows.
> return "SingleKeyValueTuple[" + cell == null ? keyPtr.get() == 
> UNITIALIZED_KEY_BUFFER ? "null" : 
> Bytes.toStringBinary(keyPtr.get(),keyPtr.getOffset(),keyPtr.getLength()) : 
> cell.toString() + "]";
> actually, the code runs in the following order.
> ("SingleKeyValueTuple[" + cell) == null ? keyPtr.get() == 
> UNITIALIZED_KEY_BUFFER ? "null" : Bytes.toStringBinary() : (cell.toString() + 
> "]");
> Therefore the result is weird.
> BTW, value = condition1 ? condition2 ? X : Y : Z is also confusing, using if 
> can be more clear.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (PHOENIX-5897) SingleKeyValueTuple.toString() returns unexpected result

2020-06-21 Thread chenglei (Jira) 


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-5897:
--
Attachment: PHOENIX-5897_v1-4.x.patch

> SingleKeyValueTuple.toString() returns unexpected result
> 
>
> Key: PHOENIX-5897
> URL: https://issues.apache.org/jira/browse/PHOENIX-5897
> Project: Phoenix
>  Issue Type: Improvement
>Affects Versions: 5.0.0-alpha
>Reporter: Chen Feng
>Assignee: Chen Feng
>Priority: Minor
> Fix For: 5.1.0
>
> Attachments: PHOENIX-5897-v1.patch, PHOENIX-5897_v1-4.x.patch
>
>
> In SingleKeyValueTuple.toString(), the code is shown as follows.
> return "SingleKeyValueTuple[" + cell == null ? keyPtr.get() == 
> UNITIALIZED_KEY_BUFFER ? "null" : 
> Bytes.toStringBinary(keyPtr.get(),keyPtr.getOffset(),keyPtr.getLength()) : 
> cell.toString() + "]";
> actually, the code runs in the following order.
> ("SingleKeyValueTuple[" + cell) == null ? keyPtr.get() == 
> UNITIALIZED_KEY_BUFFER ? "null" : Bytes.toStringBinary() : (cell.toString() + 
> "]");
> Therefore the result is weird.
> BTW, value = condition1 ? condition2 ? X : Y : Z is also confusing, using if 
> can be more clear.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)