You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey N. Gura (Jira)" <ji...@apache.org> on 2019/11/12 10:24:00 UTC
[jira] [Assigned] (IGNITE-12367) Disable by default bash
pipefail/errexit/nounset options from startup scripts
[ https://issues.apache.org/jira/browse/IGNITE-12367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey N. Gura reassigned IGNITE-12367:
---------------------------------------
Assignee: Andrey N. Gura
> Disable by default bash pipefail/errexit/nounset options from startup scripts
> -----------------------------------------------------------------------------
>
> Key: IGNITE-12367
> URL: https://issues.apache.org/jira/browse/IGNITE-12367
> Project: Ignite
> Issue Type: Bug
> Reporter: Andrey N. Gura
> Assignee: Andrey N. Gura
> Priority: Blocker
> Fix For: 2.8
>
>
> A fix for https://issues.apache.org/jira/browse/IGNITE-11216 introduced following bash options
> {noformat}
> set -o nounset
> set -o errexit
> set -o pipefail
> set -o errtrace
> set -o functrace
> {noformat}
> to Ignite startup scripts. These options cause scripts to fail immediately
> 1. on any error
> 2. on any error in child process
> 3. on any undeclared variable
> However, some, if not all non-zero errorcodes are valid and should not cause scripts to fail.
> Due to huge number of ignite startup scripts and possible configurations, risk is very high that all possible problems were not found and more to go with similar symptoms: scripts just silently exit at random.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)