-
Notifications
You must be signed in to change notification settings - Fork 38
Execution doesn't terminate even after all tasks have stopped and logs have been received #36
Comments
I have the same issue with v1.3.0 Even after the task is stopped the Cloudwatch Log Stream is polled indefinitely |
We have a similar issue that just started happening a day ago. This may be a separate root issue though:
Log events are never found ( |
Yes, having the same issue. Started 12/29. Don't know what changed, but the container exit log appears and it just keeps spitting out the "Printing events in stream" message with only "after 0". Wondering if something changed with interface against AWS API/BOTO that lead to the change in activity. Need a workaround asap. We ended up forking and modifying cloudwatch.go:
And runner.go:
To work around the issue, we added a counter since we know that after 55-ish polls our stuff completes |
Strangely, I have only been able to reproduce this in I believe there is a bug in the The documentation here, https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_FilterLogEvents.html, states:
In my tests, when we get into the state of not finding logs I posted about above, the first page has 0 events, and the I plan on writing a test that shows this behavior before submitting a PR unless someone beats me to it. |
@sherzberg did you manage to find a solution? |
Thanks for such an useful utility. It works wonderfully but in a Centos container, the binary doesn't terminate even after all tasks have stopped and logs have been received.
go version go1.13.6 linux/amd64
The text was updated successfully, but these errors were encountered: