Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D191510B94 for ; Fri, 12 Dec 2014 22:11:13 +0000 (UTC) Received: (qmail 86608 invoked by uid 500); 12 Dec 2014 22:11:13 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 86568 invoked by uid 500); 12 Dec 2014 22:11:13 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 86551 invoked by uid 99); 12 Dec 2014 22:11:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2014 22:11:13 +0000 Date: Fri, 12 Dec 2014 22:11:13 +0000 (UTC) From: "Sean Busbey (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3409) Move default ports out of ephemeral range MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244873#comment-14244873 ] Sean Busbey commented on ACCUMULO-3409: --------------------------------------- Well, it's bad form to use the ephemeral range for a non-ephemeral purpose. Some folks have restrictions on placing services in the ephemeral range. Additionally, other processes on the system are free to grab ephemeral ports at any time. By relying on a port in that range it's only a matter of chance for us to conflict on a restart. Having the monitor disappear will be confusing, though restarting it isn't hard. Having the GC fail is likely to go unnoticed until HDFS usage becomes a problem. (A minor concern is that we're also burning up possible ephemeral ports. It's only 1-2 we're talking about, but tragedy of the commons etc.) It's easy enough to change what ports get used to avoid these things proactively, we should just change the default so people don't run into this in the first place. The release note will make it relatively painless for anyone who wants to keep the old behavior to have it. > Move default ports out of ephemeral range > ----------------------------------------- > > Key: ACCUMULO-3409 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3409 > Project: Accumulo > Issue Type: Bug > Reporter: Sean Busbey > Priority: Blocker > Fix For: 2.0.0 > > > We have two components with default ports in the [IANA ephemeral range|http://tools.ietf.org/html/rfc6335#section-6]: the GC at 50091 and the monitor at 50095. We should move these to not be in the ephemeral range. > This change will be disruptive, particularly for the monitor UI port, so we should wait for a major release and include a release note that explains how to maintain the previous port choice using configuration settings in accumulo-site.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)