accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Al Krinker (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2499) User manual should include list of default ports
Date Tue, 25 Mar 2014 02:57:45 GMT


Al Krinker commented on ACCUMULO-2499:

More details per [~elserj],

Start with

This is a pretty common convention (Jetty and InetSocketAddress are two good examples in the
Java realm). When requesting to bind a socket, the port that you provide is typically used
directly to state which port you want to bind to on the interface.

When you provide '0' instead of some other valid port (e.g. 1-65535), convention states that
an ephemeral port will be chosen instead. This ephemeral port is likely to be unique and not
already bound. Thus, configuring ports to use '0' instead of some explicit value, should,
in most cases, work around any issues of running multiple distinct Accumulo instances (or
any other process which tries to use the same default ports) on the same hardware.

> User manual should include list of default ports
> ------------------------------------------------
>                 Key: ACCUMULO-2499
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: docs
>    Affects Versions: 1.5.1, 1.6.0
>            Reporter: Sean Busbey
>            Assignee: Al Krinker
>            Priority: Minor
>              Labels: firewall, newbie
>             Fix For: 1.5.2, 1.6.0
>         Attachments: ACCUMULO-2499.patch.txt
> It would be good to provide a list of the default ports used by Accumulo, so that administrators
who need to lock down network access have an easy list to crib from.
> From a mail thread, [~ecn] gave us a start
> {quote}
> Port numbers (for 1.5+)
> 4560 Accumulo monitor (for centralized log display)
> 9997 Tablet Server
> 9999 Master Server
> 12234 Accumulo Tracer
> 50091 Accumulo GC
> 50095 Accumulo HTTP monitor
> {quote}
> I'd say the [Administration -> Network|]
section would be a good fit, but maybe it should just be an appendix?

This message was sent by Atlassian JIRA

View raw message