[jira] [Commented] (HBASE-4684) REST server is leaking ZK connections in 0.90

2011-11-07 Thread Jean-Daniel Cryans (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13145571#comment-13145571
 ] 

Jean-Daniel Cryans commented on HBASE-4684:
---

Late +1, thanks for solving this Andrew!

 REST server is leaking ZK connections in 0.90
 -

 Key: HBASE-4684
 URL: https://issues.apache.org/jira/browse/HBASE-4684
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.90.4
Reporter: Jean-Daniel Cryans
Assignee: Andrew Purtell
Priority: Critical
 Fix For: 0.90.5

 Attachments: HBASE-4684-0.90.patch, HBASE-4684-v2-0.90.patch


 As reported a month ago, http://search-hadoop.com/m/FD6gmKzrxY1, the REST 
 server is leak ZK connections. Upon investigation I see that 
 TableResource.scanTransformAttrs creates a new HBA per minute per table (when 
 the server is getting requests) but never deletes the connection created in 
 there.
 There are a bunch of other places where HBAs are created but not cleaned 
 after like SchemaResource, StorageClusterStatusResource, 
 StorageClusterVersionResource, ExistsResource, etc. Those places shouldn't be 
 as leaky under normal circumstances tho.
 Thanks to Jack Levin for bringing up this issue again when he tried to 
 upgrade.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (HBASE-4684) REST server is leaking ZK connections in 0.90

2011-11-04 Thread jack levin (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13144265#comment-13144265
 ] 

jack levin commented on HBASE-4684:
---

Here is applicable patch for 0.90.4 (tested to work):

— src/main/java/org/apache/hadoop/hbase/rest/TableResource.java
+++ src/main/java/org/apache/hadoop/hbase/rest/TableResource.java
@@ -37,6 +37,7 @@
import org.apache.hadoop.hbase.HColumnDescriptor;
import org.apache.hadoop.hbase.HConstants;
import org.apache.hadoop.hbase.HTableDescriptor;
+import org.apache.hadoop.hbase.client.HConnectionManager;
import org.apache.hadoop.hbase.TableNotFoundException;
import org.apache.hadoop.hbase.client.HBaseAdmin;
import org.apache.hadoop.hbase.io.ImmutableBytesWritable;
@@ -135,6 +136,7 @@
try {
HBaseAdmin admin = new HBaseAdmin(servlet.getConfiguration());
HTableDescriptor htd = admin.getTableDescriptor(Bytes.toBytes(table));
+ HConnectionManager.deleteConnection(admin.getConfiguration(), false);
for (HColumnDescriptor hcd: htd.getFamilies()) {
for (Map.EntryImmutableBytesWritable, ImmutableBytesWritable e:
hcd.getValues().entrySet()) {

  



 REST server is leaking ZK connections in 0.90
 -

 Key: HBASE-4684
 URL: https://issues.apache.org/jira/browse/HBASE-4684
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.90.4
Reporter: Jean-Daniel Cryans
Assignee: Andrew Purtell
Priority: Critical
 Fix For: 0.90.5

 Attachments: HBASE-4684-0.90.patch, HBASE-4684-v2-0.90.patch


 As reported a month ago, http://search-hadoop.com/m/FD6gmKzrxY1, the REST 
 server is leak ZK connections. Upon investigation I see that 
 TableResource.scanTransformAttrs creates a new HBA per minute per table (when 
 the server is getting requests) but never deletes the connection created in 
 there.
 There are a bunch of other places where HBAs are created but not cleaned 
 after like SchemaResource, StorageClusterStatusResource, 
 StorageClusterVersionResource, ExistsResource, etc. Those places shouldn't be 
 as leaky under normal circumstances tho.
 Thanks to Jack Levin for bringing up this issue again when he tried to 
 upgrade.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (HBASE-4684) REST server is leaking ZK connections in 0.90

2011-11-04 Thread Andrew Purtell (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13144286#comment-13144286
 ] 

Andrew Purtell commented on HBASE-4684:
---

The patch on this issue fixes the problem and doesn't interfere with 
potentially concurrent actions.

 REST server is leaking ZK connections in 0.90
 -

 Key: HBASE-4684
 URL: https://issues.apache.org/jira/browse/HBASE-4684
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.90.4
Reporter: Jean-Daniel Cryans
Assignee: Andrew Purtell
Priority: Critical
 Fix For: 0.90.5

 Attachments: HBASE-4684-0.90.patch, HBASE-4684-v2-0.90.patch


 As reported a month ago, http://search-hadoop.com/m/FD6gmKzrxY1, the REST 
 server is leak ZK connections. Upon investigation I see that 
 TableResource.scanTransformAttrs creates a new HBA per minute per table (when 
 the server is getting requests) but never deletes the connection created in 
 there.
 There are a bunch of other places where HBAs are created but not cleaned 
 after like SchemaResource, StorageClusterStatusResource, 
 StorageClusterVersionResource, ExistsResource, etc. Those places shouldn't be 
 as leaky under normal circumstances tho.
 Thanks to Jack Levin for bringing up this issue again when he tried to 
 upgrade.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (HBASE-4684) REST server is leaking ZK connections in 0.90

2011-11-04 Thread Andrew Purtell (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13144288#comment-13144288
 ] 

Andrew Purtell commented on HBASE-4684:
---

I'm going to commit this today unless there is an objection.

 REST server is leaking ZK connections in 0.90
 -

 Key: HBASE-4684
 URL: https://issues.apache.org/jira/browse/HBASE-4684
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.90.4
Reporter: Jean-Daniel Cryans
Assignee: Andrew Purtell
Priority: Critical
 Fix For: 0.90.5

 Attachments: HBASE-4684-0.90.patch, HBASE-4684-v2-0.90.patch


 As reported a month ago, http://search-hadoop.com/m/FD6gmKzrxY1, the REST 
 server is leak ZK connections. Upon investigation I see that 
 TableResource.scanTransformAttrs creates a new HBA per minute per table (when 
 the server is getting requests) but never deletes the connection created in 
 there.
 There are a bunch of other places where HBAs are created but not cleaned 
 after like SchemaResource, StorageClusterStatusResource, 
 StorageClusterVersionResource, ExistsResource, etc. Those places shouldn't be 
 as leaky under normal circumstances tho.
 Thanks to Jack Levin for bringing up this issue again when he tried to 
 upgrade.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (HBASE-4684) REST server is leaking ZK connections in 0.90

2011-11-01 Thread Jean-Daniel Cryans (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141311#comment-13141311
 ] 

Jean-Daniel Cryans commented on HBASE-4684:
---

On the patch:

 - Instead of creating and closing HBAs, could you stick one instance in 
RESTServlet instead?
 - In its current form, the patch will need some modifications to work with 
0.90 because HBA doesn't have a close method.

bq. Still not thrilled with scan/rescan of table attributes for transformation 
directives, in retrospect.

Yeah it's kinda odd :) Not being a REST user I don't really have special 
fondness for one solution or another. The current one works.

 REST server is leaking ZK connections in 0.90
 -

 Key: HBASE-4684
 URL: https://issues.apache.org/jira/browse/HBASE-4684
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.90.4
Reporter: Jean-Daniel Cryans
Assignee: Andrew Purtell
Priority: Critical
 Fix For: 0.90.5

 Attachments: HBASE-4684-0.90.patch


 As reported a month ago, http://search-hadoop.com/m/FD6gmKzrxY1, the REST 
 server is leak ZK connections. Upon investigation I see that 
 TableResource.scanTransformAttrs creates a new HBA per minute per table (when 
 the server is getting requests) but never deletes the connection created in 
 there.
 There are a bunch of other places where HBAs are created but not cleaned 
 after like SchemaResource, StorageClusterStatusResource, 
 StorageClusterVersionResource, ExistsResource, etc. Those places shouldn't be 
 as leaky under normal circumstances tho.
 Thanks to Jack Levin for bringing up this issue again when he tried to 
 upgrade.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (HBASE-4684) REST server is leaking ZK connections in 0.90

2011-11-01 Thread Andrew Purtell (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141396#comment-13141396
 ] 

Andrew Purtell commented on HBASE-4684:
---

bq. In its current form, the patch will need some modifications to work with 
0.90 because HBA doesn't have a close method.

I'm almost positive I based this patch on the head of 0.90 branch.

bq. Instead of creating and closing HBAs, could you stick one instance in 
RESTServlet instead?

Sure, np, new patch coming soon.

Thanks for looking at the patch J-D.


 REST server is leaking ZK connections in 0.90
 -

 Key: HBASE-4684
 URL: https://issues.apache.org/jira/browse/HBASE-4684
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.90.4
Reporter: Jean-Daniel Cryans
Assignee: Andrew Purtell
Priority: Critical
 Fix For: 0.90.5

 Attachments: HBASE-4684-0.90.patch


 As reported a month ago, http://search-hadoop.com/m/FD6gmKzrxY1, the REST 
 server is leak ZK connections. Upon investigation I see that 
 TableResource.scanTransformAttrs creates a new HBA per minute per table (when 
 the server is getting requests) but never deletes the connection created in 
 there.
 There are a bunch of other places where HBAs are created but not cleaned 
 after like SchemaResource, StorageClusterStatusResource, 
 StorageClusterVersionResource, ExistsResource, etc. Those places shouldn't be 
 as leaky under normal circumstances tho.
 Thanks to Jack Levin for bringing up this issue again when he tried to 
 upgrade.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (HBASE-4684) REST server is leaking ZK connections in 0.90

2011-10-27 Thread Andrew Purtell (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13137597#comment-13137597
 ] 

Andrew Purtell commented on HBASE-4684:
---

Aha! I was looking in the wrong place.

 REST server is leaking ZK connections in 0.90
 -

 Key: HBASE-4684
 URL: https://issues.apache.org/jira/browse/HBASE-4684
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.90.4
Reporter: Jean-Daniel Cryans
Priority: Critical
 Fix For: 0.90.5


 As reported a month ago, http://search-hadoop.com/m/FD6gmKzrxY1, the REST 
 server is leak ZK connections. Upon investigation I see that 
 TableResource.scanTransformAttrs creates a new HBA per minute per table (when 
 the server is getting requests) but never deletes the connection created in 
 there.
 There are a bunch of other places where HBAs are created but not cleaned 
 after like SchemaResource, StorageClusterStatusResource, 
 StorageClusterVersionResource, ExistsResource, etc. Those places shouldn't be 
 as leaky under normal circumstances tho.
 Thanks to Jack Levin for bringing up this issue again when he tried to 
 upgrade.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (HBASE-4684) REST server is leaking ZK connections in 0.90

2011-10-27 Thread Andrew Purtell (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13137598#comment-13137598
 ] 

Andrew Purtell commented on HBASE-4684:
---

Yes, that's not good, going to rework this now.

 REST server is leaking ZK connections in 0.90
 -

 Key: HBASE-4684
 URL: https://issues.apache.org/jira/browse/HBASE-4684
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.90.4
Reporter: Jean-Daniel Cryans
Priority: Critical
 Fix For: 0.90.5


 As reported a month ago, http://search-hadoop.com/m/FD6gmKzrxY1, the REST 
 server is leak ZK connections. Upon investigation I see that 
 TableResource.scanTransformAttrs creates a new HBA per minute per table (when 
 the server is getting requests) but never deletes the connection created in 
 there.
 There are a bunch of other places where HBAs are created but not cleaned 
 after like SchemaResource, StorageClusterStatusResource, 
 StorageClusterVersionResource, ExistsResource, etc. Those places shouldn't be 
 as leaky under normal circumstances tho.
 Thanks to Jack Levin for bringing up this issue again when he tried to 
 upgrade.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira