jiangpengcheng opened a new issue #4932: URL: https://github.com/apache/openwhisk/issues/4932
when action pod's log prints like below cases: - some timestamp return 8 digit nanoseconds ``` 2020-07-17T07:28:01.911401988Z log start 2020-07-17T07:28:01.911428485Z undefined 2020-07-17T07:28:01.91164149Z XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX 2020-07-17T07:28:01.911659266Z XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX ``` in this case, the `2020-07-17T07:28:01.91164149Z` would be parsed to `2020-07-17T07:28:01.091164149Z` and will be filtered out as it's older than last timestamp, but actually it should be parsed to ``2020-07-17T07:28:01.911641490Z`` - the logs can be unordered ``` 2020-07-17T07:28:02.387244404Z log start 2020-07-17T07:28:02.387326085Z undefined 2020-07-17T07:28:02.387331028Z XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX 2020-07-17T07:28:02.387293122Z XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX ``` in this case the last log's timestamp is older than the third line, and so it will also be filtered out ------------ In both cases, the KubernetesClient will try to fetch log again but always with empty lines returned until timeout(2 seconds) We can do a benchmark to reproduce this error ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
