Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 9 Jun 2016 22:48:21 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12976910.1465401267000.46655.1465512501041@Atlassian.JIRA>
In-Reply-To: <JIRA.12976910.1465401267000@Atlassian.JIRA>
References: <JIRA.12976910.1465401267000@Atlassian.JIRA> <JIRA.12976910.1465401267102@arcas>
Subject: [jira] [Commented] (ACCUMULO-4335) Error conditions that result in
 a Halt call should ensure non-zero process exit code
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 09 Jun 2016 22:48:22 -0000


    [ https://issues.apache.org/jira/browse/ACCUMULO-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323543#comment-15323543 ] 

Sean Busbey commented on ACCUMULO-4335:
---------------------------------------

{quote}
(Note on version tagging in JIRA: it's generally safe to assume that bug which affect 1.6.5 also affect earlier versions, and I removed 2.0.0 from the fixVersion, because I think it's generally implied that any fix in one "dot zero" release will also be in future "dot zero" releases. This is my personal philosophy when triage'ing issues... but if we want to adopt some other, more reasonable standard, we could do that, too.)
{quote}

I agree, generally, but not across things that might be released at different times. For example, we could easily have a 1.9.0 after 2.0.0 comes out (if we ship 1.8.0 and 2.0.0 at about the same time), so there's no way to indicate when 2.y releases are "after" 1.w.z versions later than 1.0.0. Similarly, it's possible something would come up that causes 1.8.0 to slip and 2.0.0 to come out first.

Anywho, it's a minor issue. At some point we'll probably just have to document the history of versions.

> Error conditions that result in a Halt call should ensure non-zero process exit code
> ------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4335
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4335
>             Project: Accumulo
>          Issue Type: Bug
>          Components: gc, tserver
>    Affects Versions: 1.6.5, 1.7.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>             Fix For: 1.6.6, 1.7.2, 1.8.0
>
>         Attachments: ACCUMULO-4335-1.8.v1.patch, ACCUMULO-4335.1.patch
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> There are several places where we get some fatal error and exit with a 0 code, indicating no error.
> e.g. when the TabletServer loses the ability to monitor zk.
> (this impacts 1.6.0+, but I can only select 1.6.5 from 1.6.z)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)