You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Lars Volker (JIRA)" <ji...@apache.org> on 2017/08/02 01:37:00 UTC

[jira] [Resolved] (IMPALA-5616) Add a new flag --enable_minidumps

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

Lars Volker resolved IMPALA-5616.
---------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.10.0


IMPALA-5616: Add --enable_minidumps startup flag

If set to 'false', this flag will disable registration of the Breakpad
signal handlers during startup. The default value is 'true'. This does
not affect the ability to disable the handlers by specifying an empty
value for --minidump_path.

This change adds a test to test_breakpad.py.

Change-Id: Ie2039b9140e1c281810b27b76140e2105198bc37
Reviewed-on: http://gerrit.cloudera.org:8080/7541
Reviewed-by: Lars Volker <lv...@cloudera.com>
Tested-by: Impala Public Jenkins

> Add a new flag --enable_minidumps
> ---------------------------------
>
>                 Key: IMPALA-5616
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5616
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.10.0
>            Reporter: Lars Volker
>            Assignee: Lars Volker
>              Labels: breakpad, newbie, supportability
>             Fix For: Impala 2.10.0
>
>
> We should have an explicit flag to disable minidump support to make it easier to disable the breakpad integration. [Kudu has such a flag|https://kudu.apache.org/docs/configuration_reference.html#kudu-master_enable_minidumps], too.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)