> yarn.timeline-service.ttl-enable=true Let us validate that this is due to the TTL GC kicking in and disable the TTL flag & leave it running for a day.
Better to also verify the Tez logs of sessions hanging along waiting for the ATS to collect events (look for the last _post log file in the AM logs link). > you propose that setting that to "RollingLevelDbTimelineStore" might fix the > issue? Yes, but you would lose all the existing history, so not yet - but it will be what you need to do to get out of the TTL. Cheers, Gopal
