You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "bulolo (via GitHub)" <gi...@apache.org> on 2026/01/16 01:25:04 UTC
[I] [Bug] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
bulolo opened a new issue, #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883
### Search before asking
- [x] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
<img width="2734" height="1612" alt="Image" src="https://github.com/user-attachments/assets/0e4e5319-ecdb-422e-9400-afa748bcdf61" />
```
Caused by: java.net.UnknownHostException: dolphinscheduler-alert-67b7c695cb-v9b82
at java.net.InetAddress$CachedAddresses.get(InetAddress.java:764)
at java.net.InetAddress.getAllByName0(InetAddress.java:1291)
at java.net.InetAddress.getAllByName(InetAddress.java:1144)
at java.net.InetAddress.getAllByName(InetAddress.java:1065)
at java.net.InetAddress.getByName(InetAddress.java:1015)
at io.netty.util.internal.SocketUtils$8.run(SocketUtils.java:156)
at io.netty.util.internal.SocketUtils$8.run(SocketUtils.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at io.netty.util.internal.SocketUtils.addressByName(SocketUtils.java:153)
at io.netty.resolver.DefaultNameResolver.doResolve(DefaultNameResolver.java:41)
at io.netty.resolver.SimpleNameResolver.resolve(SimpleNameResolver.java:61)
at io.netty.resolver.SimpleNameResolver.resolve(SimpleNameResolver.java:53)
at io.netty.resolver.InetSocketAddressResolver.doResolve(InetSocketAddressResolver.java:55)
at io.netty.resolver.InetSocketAddressResolver.doResolve(InetSocketAddressResolver.java:31)
at io.netty.resolver.AbstractAddressResolver.resolve(AbstractAddressResolver.java:106)
at io.netty.bootstrap.Bootstrap.doResolveAndConnect0(Bootstrap.java:206)
```
### What you expected to happen
we can send test alert http
### How to reproduce
send a http test alsert
### Anything else
_No response_
### Version
3.3.2
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
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: commits-unsubscribe@dolphinscheduler.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "bulolo (via GitHub)" <gi...@apache.org>.
bulolo commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3757864110
the bug is :alert is not a StatefulSet,so we should not use Pod Name to registry or communicate
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "bulolo (via GitHub)" <gi...@apache.org>.
bulolo commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3757725904
network is ok in k8s:
<img width="3386" height="1486" alt="Image" src="https://github.com/user-attachments/assets/7766e840-70ef-449c-8464-5f498c1aed18" />
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "zhang-arvin (via GitHub)" <gi...@apache.org>.
zhang-arvin commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-5353979121
I'd like to work on this issue. Could you please assign it to me?
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "yeshizhu (via GitHub)" <gi...@apache.org>.
yeshizhu commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3808609326
修改helm中的alert部署为StatefulSet，创建一个alert-headless的service就可以解决
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-4173821420
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "PenneyHuang (via GitHub)" <gi...@apache.org>.
PenneyHuang commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-4562677126
The Service name must match the StatefulSet's serviceName property, and the Pods will then derive their stable network identities from the StatefulSet's controller.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "docherak (via GitHub)" <gi...@apache.org>.
docherak commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3772578475
+1
this is a bug
API Server should be using Alert Server's Service to communicate w it
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "bulolo (via GitHub)" <gi...@apache.org>.
bulolo commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3757786119
maybe is helm problem
I have analyzed the issue and the Helm templates. The problem is that DolphinScheduler components (like the Alert Server) register their pod names in the registry, which are not resolvable by other pods in Kubernetes.
i think we should use service name or ip ,not pod name in k8s,
or we can edit the yaml ,but i do not know which is the best
deployment-dolphinscheduler-alert.yaml
deployment-dolphinscheduler-api.yaml
statefulset-dolphinscheduler-master.yaml
statefulset-dolphinscheduler-worker.yaml
```
env:
- name: TZ
value: {{ .Values.timezone }}
# add
- name: IP
valueFrom:
fieldRef:
fieldPath: status.podIP
```
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "bulolo (via GitHub)" <gi...@apache.org>.
bulolo commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3757969540
same bug here :https://github.com/apache/dolphinscheduler/issues/17144
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "Gallardot (via GitHub)" <gi...@apache.org>.
Gallardot commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3772982582
> +1
>
> this is a bug
>
> API Server should be using Alert Server's Service to communicate w it
@docherak Agree. When deploying with k8s, the alert server should register its IP address to the registry center.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "shisanye13 (via GitHub)" <gi...@apache.org>.
shisanye13 commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3808616608
Modify the Alert deployment in Helm to a StatefulSet, and creating a headless Service named alert-headless will resolve the issue.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3757694193
> Caused by: java.net.UnknownHostException: dolphinscheduler-alert-67b7c695cb-v9b82
You should check your network connection.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "bulolo (via GitHub)" <gi...@apache.org>.
bulolo commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3757717719
> > Caused by: java.net.UnknownHostException: dolphinscheduler-alert-67b7c695cb-v9b82
>
> You should check your network connection.
This is not a network issue, but a Kubernetes network communication problem. I noticed that in the Helm-deployed Kubernetes cluster, none of the alert tests can complete communication. I suspect whether the correct Kubernetes cluster communication address is being used.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "bulolo (via GitHub)" <gi...@apache.org>.
bulolo commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3757722549
this is the same bug here: https://github.com/apache/dolphinscheduler/issues/16634
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "ruanwenjun (via GitHub)" <gi...@apache.org>.
ruanwenjun commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3760064340
@Gallardot PTAL
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "bulolo (via GitHub)" <gi...@apache.org>.
bulolo commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3757718093
> > Caused by: java.net.UnknownHostException: dolphinscheduler-alert-67b7c695cb-v9b82
>
> You should check your network connection.
This is not a network issue, but a Kubernetes network communication problem. I noticed that in the Helm-deployed Kubernetes cluster, none of the alert tests can complete communication. I suspect whether the correct Kubernetes cluster communication address is being used.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-3771274815
> I have analyzed the issue and the Helm templates. The problem is that DolphinScheduler components (like the Alert Server)
> register their pod names in the registry, which are not resolvable by other pods in Kubernetes.
DS cluster should be in the same pod, why should it communicate with alert server across pods?
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #17883:
URL: https://github.com/apache/dolphinscheduler/issues/17883#issuecomment-4365080664
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed] [dolphinscheduler]
Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS closed issue #17883: [Question] [Alert-http] Alert test sending failed, [Call method to Host(ip=dolphinscheduler-alert-67b7c695cb-v9b82, port=50052) failed]
URL: https://github.com/apache/dolphinscheduler/issues/17883
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org