Issue best described with some images:
Anyone have any ideas as to why, before lunch it was running and reporting taking a few seconds, now it is taking a one minute but reporting as taking 3 seconds. I am running as a data stream.
Thank you
Solved
Why is the task reporting it takes 3 seconds to run when it actually takes far longer.
+14- Contributor
- 176 replies
Best answer by virtualcitymatt
Hmmm, it could be related to the how long it takes to send the response back to the client requesting the Data Streaming service. Do you see the same thing when using data download or job submitter?
Alternatively in some cases jobs will get resubmitted in the case they crash. It could be that the job is crashing and being restatrted. This is pretty unlikely though, you can check in the processmonitor log to see if there are any crashes.
Next is to check other logs, there should be a datastreaming log I think which might give you some clues as well
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+47- Celebrity
- 2000 replies
- Best Answer
Hmmm, it could be related to the how long it takes to send the response back to the client requesting the Data Streaming service. Do you see the same thing when using data download or job submitter?
Alternatively in some cases jobs will get resubmitted in the case they crash. It could be that the job is crashing and being restatrted. This is pretty unlikely though, you can check in the processmonitor log to see if there are any crashes.
Next is to check other logs, there should be a datastreaming log I think which might give you some clues as well
+14- Contributor
- 176 replies
Hmmm, it could be related to the how long it takes to send the response back to the client requesting the Data Streaming service. Do you see the same thing when using data download or job submitter?
Alternatively in some cases jobs will get resubmitted in the case they crash. It could be that the job is crashing and being restatrted. This is pretty unlikely though, you can check in the processmonitor log to see if there are any crashes.
Next is to check other logs, there should be a datastreaming log I think which might give you some clues as well
thank you, I checked on Sunday and it was back to normal. I was using FME Cloud so wonder if there was an issue with latency to reading some s3 buckets or rds databases (both dependencies in the workbench). @stewartatsafe was there any network/performance issues with FME Cloud (Frankfurt) on Friday afternoon?
+8- Safer
- 99 replies
We did not see an elevated number of error messages in this region over the weekend. AWS did not report any issues either. I think the latency theory is a good one though and it could have been caused by issues beyond AWS. Keep an eye on it.
+14- Contributor
- 176 replies
We did not see an elevated number of error messages in this region over the weekend. AWS did not report any issues either. I think the latency theory is a good one though and it could have been caused by issues beyond AWS. Keep an eye on it.
thanks @stewartatsafe stumped us for a whole afternoon. will keep an eye, thanks