[jira] [Commented] (PHOENIX-998) SocketTimeoutException under high concurrent write access to phoenix indexed table

[ https://issues.apache.org/jira/browse/PHOENIX-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14067447#comment-14067447 ] Vikas Vishwakarma commented on PHOENIX-998: --- I was able to reproduce and

[jira] [Commented] (PHOENIX-998) SocketTimeoutException under high concurrent write access to phoenix indexed table

[ https://issues.apache.org/jira/browse/PHOENIX-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069897#comment-14069897 ] Vikas Vishwakarma commented on PHOENIX-998: --- The client does scan all the

[jira] [Commented] (PHOENIX-998) SocketTimeoutException under high concurrent write access to phoenix indexed table

[ https://issues.apache.org/jira/browse/PHOENIX-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072996#comment-14072996 ] Vikas Vishwakarma commented on PHOENIX-998: --- So this is my complete analysis:

[jira] [Created] (PHOENIX-1215) some transactions are hanging indefinitely on

Vikas Vishwakarma created PHOENIX-1215: -- Summary: some transactions are hanging indefinitely on Key: PHOENIX-1215 URL: https://issues.apache.org/jira/browse/PHOENIX-1215 Project: Phoenix

[jira] [Updated] (PHOENIX-1215) some phoenix transactions are hanging indefinitely on ps.execute() call

[ https://issues.apache.org/jira/browse/PHOENIX-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-1215: --- Summary: some phoenix transactions are hanging indefinitely on ps.execute() call

[jira] [Updated] (PHOENIX-1215) some phoenix transactions are hanging indefinitely on ps.execute() call

[ https://issues.apache.org/jira/browse/PHOENIX-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-1215: --- Description: Test Setup: == 4 load client with 16 threads each running

[jira] [Resolved] (PHOENIX-1215) some phoenix transactions are hanging indefinitely on ps.execute() call

[ https://issues.apache.org/jira/browse/PHOENIX-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma resolved PHOENIX-1215. Resolution: Invalid This turned out to be a issue in our client implementation.

[jira] [Closed] (PHOENIX-1215) some phoenix transactions are hanging indefinitely on ps.execute() call

[ https://issues.apache.org/jira/browse/PHOENIX-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma closed PHOENIX-1215. -- This turned out to be a issue in our client implementation. Closing. some phoenix

[jira] [Updated] (PHOENIX-4044) Orphaned chunk bytes found warnings during finalize in GlobalMemoryManager

[ https://issues.apache.org/jira/browse/PHOENIX-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-4044: --- Summary: Orphaned chunk bytes found warnings during finalize in GlobalMemoryManager

[jira] [Updated] (PHOENIX-4044) Orphaned chunk bytes found during finalize in

[ https://issues.apache.org/jira/browse/PHOENIX-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-4044: --- Summary: Orphaned chunk bytes found during finalize in (was: Orphaned chunk of

[jira] [Created] (PHOENIX-4044) Orphaned chunk of 15650000 bytes found during finalize

Vikas Vishwakarma created PHOENIX-4044: -- Summary: Orphaned chunk of 1565 bytes found during finalize Key: PHOENIX-4044 URL: https://issues.apache.org/jira/browse/PHOENIX-4044 Project: Phoenix

[jira] [Commented] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372409#comment-16372409 ] Vikas Vishwakarma commented on PHOENIX-4625: [~larsh] [~giacomotaylor] this is one of the

[jira] [Updated] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-4625: --- Description: We have two different code path # In ConnectionQueryServicesImpl 

[jira] [Updated] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-4625: --- Affects Version/s: (was: 4.13.0) 4.14.0 > memory leak in

[jira] [Updated] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-4625: --- Attachment: PHOENIX-4625.patch > memory leak in PhoenixConnection if scanner renew

[jira] [Updated] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-4625: --- Description: We have two different code path # In ConnectionQueryServicesImpl 

[jira] [Commented] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372438#comment-16372438 ] Vikas Vishwakarma commented on PHOENIX-4625: [~jamestaylor] please review just replaced

[jira] [Updated] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-4625: --- Attachment: GC_Leak.png > memory leak in PhoenixConnection if scanner renew lease

[jira] [Updated] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-4625: --- Attachment: GC_After_fix.png > memory leak in PhoenixConnection if scanner renew

[jira] [Created] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

Vikas Vishwakarma created PHOENIX-4625: -- Summary: memory leak in PhoenixConnection if scanner renew lease thread is not enabled Key: PHOENIX-4625 URL: https://issues.apache.org/jira/browse/PHOENIX-4625

[jira] [Updated] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Vishwakarma updated PHOENIX-4625: --- Attachment: QS.png > memory leak in PhoenixConnection if scanner renew lease thread

[jira] [Commented] (PHOENIX-4625) memory leak in PhoenixConnection if scanner renew lease thread is not enabled

[ https://issues.apache.org/jira/browse/PHOENIX-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372460#comment-16372460 ] Vikas Vishwakarma commented on PHOENIX-4625: Tested locally , attached the GC graphs with