You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hop.apache.org by "usbrandon (via GitHub)" <gi...@apache.org> on 2023/03/09 04:33:03 UTC
[GitHub] [hop] usbrandon opened a new issue, #2530: [Bug]: Remote Execution of workflows does not work because it tries to connect to 127.0.0.1
usbrandon opened a new issue, #2530:
URL: https://github.com/apache/hop/issues/2530
### Apache Hop version?
2.4.0-SNAPSHOT (2023-03-08 07.37.34)
### Java version?
11
### Operating system
Windows
### What happened?
I ran a simple workflow that runs a pipeline that outputs 10 rows to the logs. If you remote run the pipeline (export resources), it works fine. If you try to remote run the workflow, it seems to connect to the remote hop server, but when it tries to run the pipeline, for whatever reason the remote server tries to connect to itself using 127.0.0.1 instead of the IP address the server bound itself to.
If it could bind both to localhost and the host IP maybe this would be fine. Shouldn't hop-server try that to begin with? Alternatively, why wouldn't the server try to run whatever pipelines and workloads against the bound IP that was called to get things going?
### Issue Priority
Priority: 2
### Issue Component
Component: Hop Server
--
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.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [hop] usbrandon commented on issue #2530: [Bug]: Remote Execution of workflows does not work because it tries to connect to 127.0.0.1
Posted by "usbrandon (via GitHub)" <gi...@apache.org>.
usbrandon commented on issue #2530:
URL: https://github.com/apache/hop/issues/2530#issuecomment-1461268339
[simple-pipe.zip](https://github.com/apache/hop/files/10927831/simple-pipe.zip)
Workflow and pipeline for reproduction
--
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.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [hop] usbrandon commented on issue #2530: [Bug]: Remote Execution of workflows does not work because it tries to connect to 127.0.0.1
Posted by "usbrandon (via GitHub)" <gi...@apache.org>.
usbrandon commented on issue #2530:
URL: https://github.com/apache/hop/issues/2530#issuecomment-1462495050
I figured out this is a ME problem. Hop does not make it visible to users what pipelines on the workflow canvas will use to execute. When using a remote config for the workflow, all the pipelines may magically decide they will try to execute remotely too. In reality, we want to run the workflow remotely and when it lands, everything it does runs "local" to the remote server.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [hop] usbrandon closed issue #2530: [Bug]: Remote Execution of workflows does not work because it tries to connect to 127.0.0.1
Posted by "usbrandon (via GitHub)" <gi...@apache.org>.
usbrandon closed issue #2530: [Bug]: Remote Execution of workflows does not work because it tries to connect to 127.0.0.1
URL: https://github.com/apache/hop/issues/2530
--
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.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org