Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Impala 2.6.0
    • Fix Version/s: Impala 2.7.0
    • Component/s: Backend
    • Labels:
      None
    • Docs Text:
      Hide
      Let's consider documenting this as a new debugging capability for expert admins. I don't think it would be very popular as it's pretty low level, but in the past we were criticized by expert admins about our lack of documentation around more advanced troubleshooting capabilities, such as the /memz page and such.
      Show
      Let's consider documenting this as a new debugging capability for expert admins. I don't think it would be very popular as it's pretty low level, but in the past we were criticized by expert admins about our lack of documentation around more advanced troubleshooting capabilities, such as the /memz page and such.
    • Target Version:

      Description

      IMPALA-3538 outlines different possible ways to manually trigger writing a minidump file. This Jira tracks writing minidump files when receiving SIGUSR1. Currently we don't use SIGUSR1 for anything else.

        Issue Links

          Activity

          Hide
          lv Lars Volker added a comment -

          bharath v - I think this would help us debug hangs / freezes by being able to trigger minidump creation. Is there a way to include this in 2.6.2?

          Show
          lv Lars Volker added a comment - bharath v - I think this would help us debug hangs / freezes by being able to trigger minidump creation. Is there a way to include this in 2.6.2?
          Hide
          lv Lars Volker added a comment -

          Harrison Sheinblatt - I would like to suggest including this in 2.6.2. Is there anything I need to do for that besides setting the target version?

          Show
          lv Lars Volker added a comment - Harrison Sheinblatt - I would like to suggest including this in 2.6.2. Is there anything I need to do for that besides setting the target version?
          Hide
          lv Lars Volker added a comment -

          IMPALA-3677: Write minidump on SIGUSR1

          Sending SIGUSR1 to any of the impala daemons (catalogd, impalad,
          statestored) will trigger a minidump write.

          The hotspot JVM also uses SIGUSR1 internally. However the documentation
          explains, that existing signal handlers will be transparently wrapped by
          the JVM and no spurious signals should be received by the daemon signal
          handler:
          http://www.oracle.com/technetwork/java/javase/signals-139944.html

          Example: killall -SIGUSR1 catalogd

          Change-Id: I40149e48e391451de21a5c8bda18e2307fc89513
          Reviewed-on: http://gerrit.cloudera.org:8080/3312
          Reviewed-by: Lars Volker <lv@cloudera.com>
          Tested-by: Internal Jenkins

          Show
          lv Lars Volker added a comment - IMPALA-3677 : Write minidump on SIGUSR1 Sending SIGUSR1 to any of the impala daemons (catalogd, impalad, statestored) will trigger a minidump write. The hotspot JVM also uses SIGUSR1 internally. However the documentation explains, that existing signal handlers will be transparently wrapped by the JVM and no spurious signals should be received by the daemon signal handler: http://www.oracle.com/technetwork/java/javase/signals-139944.html Example: killall -SIGUSR1 catalogd Change-Id: I40149e48e391451de21a5c8bda18e2307fc89513 Reviewed-on: http://gerrit.cloudera.org:8080/3312 Reviewed-by: Lars Volker <lv@cloudera.com> Tested-by: Internal Jenkins

            People

            • Assignee:
              lv Lars Volker
              Reporter:
              lv Lars Volker
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development