accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-4335) Error conditions that result in a Halt call should ensure non-zero process exit code
Date Wed, 08 Jun 2016 15:59:21 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sean Busbey updated ACCUMULO-4335:
----------------------------------
    Attachment: ACCUMULO-4335.1.patch

-01

  - went through `Halt.halt(String)` calls and ensured errors switch to `Halt.halt(String,
1)`
  - updated TServer LockWatcher to use exit code 1 (like the other server processes)

> 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.8.0, 2.0.0
>
>         Attachments: ACCUMULO-4335.1.patch
>
>
> 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)

Mime
View raw message