accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corey J. Nolet (JIRA)" <>
Subject [jira] [Comment Edited] (ACCUMULO-1393) Removed code related to default ports in client code
Date Wed, 15 May 2013 03:51:15 GMT


Corey J. Nolet edited comment on ACCUMULO-1393 at 5/15/13 3:50 AM:

Just to be clear, are we referring to the this method in the ServerServices? 

    // not necessary: everything should be advertizing ports in zookeeper
    int getDefaultPort() {
      switch (this) {
        case TSERV_CLIENT:
          return AccumuloConfiguration.getDefaultConfiguration().getPort(Property.TSERV_CLIENTPORT);
        case MASTER_CLIENT:
          return AccumuloConfiguration.getDefaultConfiguration().getPort(Property.MASTER_CLIENTPORT);
        case GC_CLIENT:
          return AccumuloConfiguration.getDefaultConfiguration().getPort(Property.GC_PORT);
          throw new IllegalArgumentException();

      was (Author: sonixbp):
    Just to be clear, are we referring to the the MasterClient's call to 
{code}int portHint = instance.getConfiguration().getPort(Property.MASTER_CLIENTPORT);{code}

And the fact that Property.MASTER_CLIENTPORT has a default port of 9999?

> Removed code related to default ports in client code
> ----------------------------------------------------
>                 Key: ACCUMULO-1393
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Keith Turner
>            Assignee: Corey J. Nolet
>             Fix For: 1.6.0
> The Accumulo client code has code for dealing with default master and tserver ports.
 This code is old and unused.  Its always expected that locations listed in zookeeper and
the metadata table will have a ip+port now.  If this expectation is not met, it should be
treated as an error instead of falling back to a default.  Removing this code would clean
up the client and logging produced by the client.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message