Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 2.8.1
-
Fix Version/s: 2.9.0, 3.0.0-beta1, 2.8.2
-
Component/s: log-aggregation
-
Labels:None
-
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.