Forum Discussion

Vladyslav's avatar
Vladyslav
New Contributor
4 years ago

Issue (or bug) with mapper snap

Hello, I have found something like bug. I cannot understand the strange result of the following pipeline. When I run validation of this pipeline, I see following results. As expected count...
jjenkins1's avatar
jjenkins1
New Contributor
3 years ago
Copy LinkReport

Hi RavNeu,

Did you ever figure out why you received the error?

Failure: REST API service endpoint returned error result: status code = 400, Reason: REST API service endpoint returned error result: status code = 400, reason phrase = BAD REQUEST, refer to the error_entity field in the error view document for more details, Resolution: Please check the values of Snap properties.

joel_bourgault's avatar
joel_bourgault
New Contributor III
3 years ago
Copy LinkReport

Hi All,
Just to share my experience: to retrieve runtime statuses, I use the following endpoint: https://elastic.snaplogic.com/api/1/rest/public/runtime/%1$s?last_hours=%2$s&limit=%3$s&offset=%4$s, that I call .sprintf() on it with following variables:

  • %1$s is replaced by my Org
  • %2$s is replaced by a number of hours from now in the past
  • %3$s and %4$s are used by pagination

This is associated with my personal account, stored as REST Basic Auth account.

Hope this helps!

  • christwr's avatar
    christwr
    Contributor III
    7 years ago
    Copy LinkReport

    The load balancer would be to select which groundplex node to submit the initial request to. You don’t want to always point to some specific node, as it may be down at any given point for maintenance, etc. The load balancer would send to one of the groundplex nodes that are actually up and accepting requests.

    To provide redundancy across all nodes in the Groundplex when a triggered task is invoked, a load balancer can be placed in front of the Groundplex nodes

  • ram3's avatar
    ram3
    New Contributor
    3 years ago
    Copy LinkReport

    @tlikarish @cjhoward18 Thank you for this blog post. My understanding is, if we use the Cloud URL then there is no need to setup the “GP_LB” right ? I am saying this because, Control plane has the information of which node is available and least loaded (has resources) to run the task & also has information of whether the task is already cached in the node.

    Additionally, do you discourage the triggering of tasks using Cloud URL for security reasons ? If so, how to disable the CloudURL. Thanks in advance