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

NM failed to perform log aggregation due to absent container

          Details

          • Target Version/s:

            Description

            Saw a case where the NM failed to aggregate the logs for a container because it claimed it was absent:

            2017-08-23 18:35:38,283 [AsyncDispatcher event handler] WARN logaggregation.LogAggregationService: Log aggregation cannot be started for container_e07_1503326514161_502342_01_000001, as its an absent container

            Containers should not be allowed to disappear if they're not done being fully processed by the NM.

              Attachments

              1. YARN-7087.001.patch
                21 kB
                Jason Lowe
              2. YARN-7087.002.patch
                22 kB
                Jason Lowe

                Issue Links

                relates to

                Sub-task - The sub-task of the issue YARN-221 NM should provide a way for AM to tell it not to aggregate logs.

                • Major - Major loss of function.
                • Resolved

                Bug - A problem which impairs or prevents the functions of the product. YARN-4152 NM crash with NPE when LogAggregationService#stopContainer called for absent container

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

                  Activity

                    People

                    • Assignee:
                      jlowe Jason Lowe
                      Reporter:
                      jlowe Jason Lowe
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      5 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: