Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-4021

RuntimeException/YarnRuntimeException sent over to the client can cause client to assume a local fatal failure

        Details

        • Type: Bug
        • Status: Open
        • Priority: Major
        • Resolution: Unresolved
        • Affects Version/s: None
        • Fix Version/s: None
        • Component/s: None
        • Labels:
          None
        • Target Version/s:
        • Hadoop Flags:
          Incompatible change

          Description

          Currently RuntimeException and its derived types such as YarnRuntimeExceptions are serialized over to the client and thrown at the client after YARN-731. This can cause issues like MAPREDUCE-6439 where we assume a local fatal exception has happened.
          Instead we should have a way to distinguish local RuntimeException versus remote RuntimeException to avoid these issues. We need to go over all the current client side code that is expecting a remote RuntimeException inorder to make it work with this change.

            Issue Links

            is related to

            Bug - A problem which impairs or prevents the functions of the product. MAPREDUCE-6439 AM may fail instead of retrying if RM shuts down during the allocate call

            • Critical - Crashes, loss of data, severe memory leak.
            • Closed

              Activity

              There are no comments yet on this issue.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  adhoot Anubhav Dhoot
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:

                    Development