New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The logs in activation is not complete #2548
Comments
Just to avoid any doubt, we tried below too. We see the lines printed directly to System.out and System.err were missing too.
|
Thanks for the additional details. I'll try to reproduce and address. Can you confirm that you observe the activation results are all successful (no killed actions)? We have a theory which I'll try to test. |
Yes, I confirm that the activation results are successful for those I inspected. I didn't inspect all since there were thousands activation. |
This is what it looks like for one of those activation (I truncated some of the log lines as they were very long):
|
Hi, just want to follow up on the progress of this defect and see if there is any update? Thanks. |
Hi, is there any progress on the issue? Thanks. |
@andrewnet I did not manage to reproduce this - are you still encountering truncated log issues? |
Hi @rabbah , yes, we still see the problem. In the last run we did yesterday, 293 out of 28794 activation do not have full log. |
I have added log frame markers to the Java runtime apache/openwhisk-runtime-java#63; their absence doesn't necessarily cause log truncation, but the markers do explicitly flush the streams. |
Environment details:
Steps to reproduce the issue:
This happens randomly. Most activation contain complete logs however some activation do not have complete logs. The entry point of our OpenWhisk java action looks like below. So if the logs in activation contains the complete log, you should see
Exit WhiskMain, resp=...
in the logs; this is not the case for all the activation.We checked the response object in the activation, it contains the right object that prove the activation finished properly.
Provide the expected results and outputs:
We should always see
Exit WhiskMain, resp=...
in the logs of activation.Provide the actual results and outputs:
The logs in activation only contains some of the logs and the line
Exit WhiskMain, resp=...
doesn't show up in some of the activation (while others do)Additional information you deem important:
This problem is blocking us to release our product, as we need the complete log to troubleshooting why activation didn't go as we expected.
The text was updated successfully, but these errors were encountered: