You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Barney Frank (JIRA)" <ji...@apache.org> on 2009/09/16 02:04:57 UTC
[jira] Created: (HBASE-1842) HTablePool -- Ride Over Restart
HTablePool -- Ride Over Restart
-------------------------------
Key: HBASE-1842
URL: https://issues.apache.org/jira/browse/HBASE-1842
Project: Hadoop HBase
Issue Type: Bug
Components: client
Affects Versions: 0.20.0
Environment: Configuration:
Hbase 0.20.0 & Hadoop 0.20.1
Pseudo distributed mode
Java client using HTablePool
Reporter: Barney Frank
When ZK, Master, Regionserver and my app are running, I stop the Hbase master/regionserver. The HBaseClient then begins to complain:
16:26:51,273 INFO [HBaseClient] Retrying connect to server: /192.168.1.55:44808. Already tried 0 time(s).
16:26:53,274 INFO [HBaseClient] Retrying connect to server: /192.168.1.55:44808. Already tried 1 time(s).
...already tried 9 time(s)....
16:27:10,294 INFO [HbaseRPC] Server at /192.168.1.55:44808 not available yet, Zzzzz...
I restart the Master and RegionServer and then send more client requests through HTablePool. It has the same "Retrying to connect to server:" messages. I noticed that the port number it is using is the old port for the region server and not the new one assigned after the restart. The HbaseClient does not seem to recover unless I restart the client app. When I do not use HTablePool and only Htable it works fine.
When using HTablePool, the client doesn't seem to refresh with the new regionserver port after the master/regions are back up. It gets "stuck" with the info from the settings prior to the master going down. The ability to ride over a restart.
I would appreciate any thoughts or help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1842) HTablePool -- Ride Over Restart
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758488#action_12758488 ]
stack commented on HBASE-1842:
------------------------------
In standalone mode, regionserver ports are randomly chosen so as not to clash since all daemons are running in the one JVM on the one host. Are you sure you were running pseudo-distributed mode Barney? I didn't think we did randomly-chosen ports in this mode? Changing regionserver ports under a running client is not something that the client will adjust to automatically and is not something that happens usually at least in fully distributed mode. What happens if you do fully-distributed mode, stop the cluster on client and then retry (Or, after retry, tell the client that the ports have changed by setting the port in the Configuration passed to HTablePool).
> HTablePool -- Ride Over Restart
> -------------------------------
>
> Key: HBASE-1842
> URL: https://issues.apache.org/jira/browse/HBASE-1842
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.20.0
> Environment: Configuration:
> Hbase 0.20.0 & Hadoop 0.20.1
> Pseudo distributed mode
> Java client using HTablePool
> Reporter: Barney Frank
> Fix For: 0.20.1
>
>
> When ZK, Master, Regionserver and my app are running, I stop the Hbase master/regionserver. The HBaseClient then begins to complain:
> 16:26:51,273 INFO [HBaseClient] Retrying connect to server: /192.168.1.55:44808. Already tried 0 time(s).
> 16:26:53,274 INFO [HBaseClient] Retrying connect to server: /192.168.1.55:44808. Already tried 1 time(s).
> ...already tried 9 time(s)....
> 16:27:10,294 INFO [HbaseRPC] Server at /192.168.1.55:44808 not available yet, Zzzzz...
> I restart the Master and RegionServer and then send more client requests through HTablePool. It has the same "Retrying to connect to server:" messages. I noticed that the port number it is using is the old port for the region server and not the new one assigned after the restart. The HbaseClient does not seem to recover unless I restart the client app. When I do not use HTablePool and only Htable it works fine.
> When using HTablePool, the client doesn't seem to refresh with the new regionserver port after the master/regions are back up. It gets "stuck" with the info from the settings prior to the master going down. The ability to ride over a restart.
> I would appreciate any thoughts or help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1842) HTablePool -- Ride Over Restart
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1842:
-------------------------
Fix Version/s: 0.20.1
Look at in 0.20.1.
> HTablePool -- Ride Over Restart
> -------------------------------
>
> Key: HBASE-1842
> URL: https://issues.apache.org/jira/browse/HBASE-1842
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.20.0
> Environment: Configuration:
> Hbase 0.20.0 & Hadoop 0.20.1
> Pseudo distributed mode
> Java client using HTablePool
> Reporter: Barney Frank
> Fix For: 0.20.1
>
>
> When ZK, Master, Regionserver and my app are running, I stop the Hbase master/regionserver. The HBaseClient then begins to complain:
> 16:26:51,273 INFO [HBaseClient] Retrying connect to server: /192.168.1.55:44808. Already tried 0 time(s).
> 16:26:53,274 INFO [HBaseClient] Retrying connect to server: /192.168.1.55:44808. Already tried 1 time(s).
> ...already tried 9 time(s)....
> 16:27:10,294 INFO [HbaseRPC] Server at /192.168.1.55:44808 not available yet, Zzzzz...
> I restart the Master and RegionServer and then send more client requests through HTablePool. It has the same "Retrying to connect to server:" messages. I noticed that the port number it is using is the old port for the region server and not the new one assigned after the restart. The HbaseClient does not seem to recover unless I restart the client app. When I do not use HTablePool and only Htable it works fine.
> When using HTablePool, the client doesn't seem to refresh with the new regionserver port after the master/regions are back up. It gets "stuck" with the info from the settings prior to the master going down. The ability to ride over a restart.
> I would appreciate any thoughts or help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1842) HTablePool -- Ride Over Restart
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1842:
-------------------------
Fix Version/s: (was: 0.20.1)
Moving out of 0.20.1. This doesn't seem like an issue of import given the above. HBASE-1815 should help with the more general issue of client recovering on cluster restart.
> HTablePool -- Ride Over Restart
> -------------------------------
>
> Key: HBASE-1842
> URL: https://issues.apache.org/jira/browse/HBASE-1842
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.20.0
> Environment: Configuration:
> Hbase 0.20.0 & Hadoop 0.20.1
> Pseudo distributed mode
> Java client using HTablePool
> Reporter: Barney Frank
>
> When ZK, Master, Regionserver and my app are running, I stop the Hbase master/regionserver. The HBaseClient then begins to complain:
> 16:26:51,273 INFO [HBaseClient] Retrying connect to server: /192.168.1.55:44808. Already tried 0 time(s).
> 16:26:53,274 INFO [HBaseClient] Retrying connect to server: /192.168.1.55:44808. Already tried 1 time(s).
> ...already tried 9 time(s)....
> 16:27:10,294 INFO [HbaseRPC] Server at /192.168.1.55:44808 not available yet, Zzzzz...
> I restart the Master and RegionServer and then send more client requests through HTablePool. It has the same "Retrying to connect to server:" messages. I noticed that the port number it is using is the old port for the region server and not the new one assigned after the restart. The HbaseClient does not seem to recover unless I restart the client app. When I do not use HTablePool and only Htable it works fine.
> When using HTablePool, the client doesn't seem to refresh with the new regionserver port after the master/regions are back up. It gets "stuck" with the info from the settings prior to the master going down. The ability to ride over a restart.
> I would appreciate any thoughts or help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-1842) HTablePool -- Ride Over Restart
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-1842.
--------------------------
Resolution: Duplicate
Marking as duplicate of hbase-1815
> HTablePool -- Ride Over Restart
> -------------------------------
>
> Key: HBASE-1842
> URL: https://issues.apache.org/jira/browse/HBASE-1842
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.20.0
> Environment: Configuration:
> Hbase 0.20.0 & Hadoop 0.20.1
> Pseudo distributed mode
> Java client using HTablePool
> Reporter: Barney Frank
>
> When ZK, Master, Regionserver and my app are running, I stop the Hbase master/regionserver. The HBaseClient then begins to complain:
> 16:26:51,273 INFO [HBaseClient] Retrying connect to server: /192.168.1.55:44808. Already tried 0 time(s).
> 16:26:53,274 INFO [HBaseClient] Retrying connect to server: /192.168.1.55:44808. Already tried 1 time(s).
> ...already tried 9 time(s)....
> 16:27:10,294 INFO [HbaseRPC] Server at /192.168.1.55:44808 not available yet, Zzzzz...
> I restart the Master and RegionServer and then send more client requests through HTablePool. It has the same "Retrying to connect to server:" messages. I noticed that the port number it is using is the old port for the region server and not the new one assigned after the restart. The HbaseClient does not seem to recover unless I restart the client app. When I do not use HTablePool and only Htable it works fine.
> When using HTablePool, the client doesn't seem to refresh with the new regionserver port after the master/regions are back up. It gets "stuck" with the info from the settings prior to the master going down. The ability to ride over a restart.
> I would appreciate any thoughts or help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.