This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Has anyone observed issues with dashboard and logging?

krupalibshah
Contributor

‎04-05-2018 02:28 AM

We observe the error if occurs should occur at the first snap but what is shown in pipeline statistics it is appearing in after 1st snap. The errors occurring on REST snap is shown on MAPPER and vice versa. Please see the screenshots.

image

image

0 Kudos
Reply
2 REPLIES 2

stephenknilans
Contributor

‎04-05-2018 06:18 AM

Several parts of the pipeline can run at once, so it is possible that they may show you errors simultaneously. If one fails fatally, it will stop others, and they may then fail if they were in the middle of something.

Obviously, the behavior of the effects of these errors could seem to be random, based on the data and the speed of the various processes.

What COULD have happened above is that payload wasn’t returned, which caused that payload error, and it may have stopped the rest call just as it was trying to connect, and you got that error. Other snaps may have finished, or didn’t start, or flushed their caches, etc… and just say they were aborted.

0 Kudos
Reply

krupalibshah
Contributor
In response to stephenknilans

‎04-05-2018 06:51 AM

Not worried about the other snap’s behavior but the error message here is irrelevant.

Mapper snap can not get REST API 503 error
REST SNAP can not give error for mapper.

The sequence is mapper->rest get

so if mapper fails due to $payload is undefined that error can not go to rest get.

Also the above screenshots are from different execution cycle due to same error, so both behavior is expected to be same.

0 Kudos
Reply