You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/12/30 08:00:50 UTC
[GitHub] [pulsar] lichuan6 opened a new issue #9092: Function worker service is not done initializing
lichuan6 opened a new issue #9092:
URL: https://github.com/apache/pulsar/issues/9092
**Describe the bug**
I have a pulsar cluster deployed in EKS. I was trying to run `functions` or `sinks` sub commands, but I got annoying errors.
The commands and errors are:
`functions list`
```shell
export TOKEN="xxxxx" # token generate from Pulsar Admin UI
bin/pulsar-admin --admin-url http://pulsar-broker.pulsar:8080 --auth-params "token:${ADMIN_JWT_TOKEN}" --auth-plugin "org.apache.pulsar.client.impl.auth.AuthenticationToken" functions list
```
`sinks list`
```shell
export TOKEN="xxxxx" # token generate from Pulsar Admin UI
bin/pulsar-admin --admin-url http://pulsar-broker.pulsar:8080 --auth-params "token:${ADMIN_JWT_TOKEN}" --auth-plugin "org.apache.pulsar.client.impl.auth.AuthenticationToken" sinks list
```
error:
```
Function worker service is not done initializing. Please try again in a little while.
Reason: HTTP 503 Service Unavailable
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] freeznet edited a comment on issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
freeznet edited a comment on issue #9092:
URL: https://github.com/apache/pulsar/issues/9092#issuecomment-752887079
Can you provide more details about how you deploy your cluster? Also when you execute `functions ls` command, can you see any log from broker pod?
usually we suggest you interact with your cluster through `pulsar-proxy`, but not directly to your `broker`. If you want connect to your `broker` directly, you should make sure your `broker` have function worker service enabled.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] freeznet commented on issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
freeznet commented on issue #9092:
URL: https://github.com/apache/pulsar/issues/9092#issuecomment-752887079
Can you provide more details about how you deploy your cluster? Also when you execute `functions ls` command, can you see any log from broker pod?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] codelipenghui closed issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
codelipenghui closed issue #9092:
URL: https://github.com/apache/pulsar/issues/9092
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] lichuan6 edited a comment on issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
lichuan6 edited a comment on issue #9092:
URL: https://github.com/apache/pulsar/issues/9092#issuecomment-753835188
After changing the token generated from pulsar UI to the one in `broker.conf`, I can call `functions list` successfully.
Then I succeeded to create a sink using `sinks create`, however, I got this error when trying to stats the sink.
In toolset pod:
```shell
bin/pulsar-admin --admin-url http://pulsar-broker.pulsar:8080 --auth-params "token:${TOKEN}" --auth-plugin "org.apache.pulsar.client.impl.auth.AuthenticationToken" sinks status --tenant public --namespace default --name my-elasticsearch-sink
{
"numInstances" : 1,
"numRunning" : 0,
"instances" : [ {
"instanceId" : 0,
"status" : {
"running" : false,
"error" : "UNAVAILABLE: Unable to resolve host pf-public-default-my-elasticsearch-sink-0.pf-public-default-my-elasticsearch-sink.pulsar.svc.cluster.local",
"numRestarts" : 0,
"numReadFromPulsar" : 0,
"numSystemExceptions" : 0,
"latestSystemExceptions" : [ ],
"numSinkExceptions" : 0,
"latestSinkExceptions" : [ ],
"numWrittenToSink" : 0,
"lastReceivedTime" : 0,
"workerId" : "c-2.6.1-pulsar-fw-pulsar-broker-4.pulsar-broker.pulsar.svc.cluster.local-8080"
}
} ]
}
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] yan0727 commented on issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
yan0727 commented on issue #9092:
URL: https://github.com/apache/pulsar/issues/9092#issuecomment-943161647
@lichuan6 I also made this mistake, but I didn't understand how you solved 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@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] wolfstudy commented on issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
wolfstudy commented on issue #9092:
URL: https://github.com/apache/pulsar/issues/9092#issuecomment-753923726
> "error" : "UNAVAILABLE: Unable to resolve host pf-public-default-my-elasticsearch-sink-0.pf-public-default-my-elasticsearch-sink.pulsar.svc.cluster.local",
This is because your terminal cannot connect to the ip address in the pod. You can use ping or telnet to verify. Under normal circumstances, this network connection is not working. You can consider the following solutions:
- If it is a test environment, you can use kubectl exec -it <your pod name>, enter the pod, and then execute the above command.
- If it is a production environment, you can consider using DNS and other methods to expose the address to be accessed
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] lichuan6 commented on issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
lichuan6 commented on issue #9092:
URL: https://github.com/apache/pulsar/issues/9092#issuecomment-753835188
After changing the token generated from pulsar UI to the one in `broker.conf`, I can call `functions list` successfully.
Then I tried to create a sink using `sinks create`, however, I got this error when trying to stats the sink.
In toolset pod:
```shell
bin/pulsar-admin --admin-url http://pulsar-broker.pulsar:8080 --auth-params "token:${TOKEN}" --auth-plugin "org.apache.pulsar.client.impl.auth.AuthenticationToken" sinks status --tenant public --namespace default --name my-elasticsearch-sink
{
"numInstances" : 1,
"numRunning" : 0,
"instances" : [ {
"instanceId" : 0,
"status" : {
"running" : false,
"error" : "UNAVAILABLE: Unable to resolve host pf-public-default-my-elasticsearch-sink-0.pf-public-default-my-elasticsearch-sink.pulsar.svc.cluster.local",
"numRestarts" : 0,
"numReadFromPulsar" : 0,
"numSystemExceptions" : 0,
"latestSystemExceptions" : [ ],
"numSinkExceptions" : 0,
"latestSinkExceptions" : [ ],
"numWrittenToSink" : 0,
"lastReceivedTime" : 0,
"workerId" : "c-2.6.1-pulsar-fw-pulsar-broker-4.pulsar-broker.pulsar.svc.cluster.local-8080"
}
} ]
}
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] lichuan6 commented on issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
lichuan6 commented on issue #9092:
URL: https://github.com/apache/pulsar/issues/9092#issuecomment-758510936
After killing broker pods and waiting for hours, my own sink connector ran successfully.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] lichuan6 edited a comment on issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
lichuan6 edited a comment on issue #9092:
URL: https://github.com/apache/pulsar/issues/9092#issuecomment-753835188
@freeznet Thanks for you reply.
After changing the token generated from pulsar UI to the one in `broker.conf`, I can call `functions list` successfully.
Then I succeeded to create a sink using `sinks create`, however, I got this error when trying to stats the sink.
In toolset pod:
```shell
bin/pulsar-admin --admin-url http://pulsar-broker.pulsar:8080 --auth-params "token:${TOKEN}" --auth-plugin "org.apache.pulsar.client.impl.auth.AuthenticationToken" sinks status --tenant public --namespace default --name my-elasticsearch-sink
{
"numInstances" : 1,
"numRunning" : 0,
"instances" : [ {
"instanceId" : 0,
"status" : {
"running" : false,
"error" : "UNAVAILABLE: Unable to resolve host pf-public-default-my-elasticsearch-sink-0.pf-public-default-my-elasticsearch-sink.pulsar.svc.cluster.local",
"numRestarts" : 0,
"numReadFromPulsar" : 0,
"numSystemExceptions" : 0,
"latestSystemExceptions" : [ ],
"numSinkExceptions" : 0,
"latestSinkExceptions" : [ ],
"numWrittenToSink" : 0,
"lastReceivedTime" : 0,
"workerId" : "c-2.6.1-pulsar-fw-pulsar-broker-4.pulsar-broker.pulsar.svc.cluster.local-8080"
}
} ]
}
```
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] wolfstudy edited a comment on issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
wolfstudy edited a comment on issue #9092:
URL: https://github.com/apache/pulsar/issues/9092#issuecomment-753923726
> "error" : "UNAVAILABLE: Unable to resolve host pf-public-default-my-elasticsearch-sink-0.pf-public-default-my-elasticsearch-sink.pulsar.svc.cluster.local",
This is because your terminal cannot connect to the ip address in the pod. You can use ping or telnet to verify. Under normal circumstances, this network connection is not working. You can consider the following solutions:
- If it is a test environment, you can use `kubectl exec -it <your pod name>`, enter the pod, and then execute the above command.
- If it is a production environment, you can consider using DNS and other methods to expose the address to be accessed
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] codelipenghui commented on issue #9092: Function worker service is not done initializing
Posted by GitBox <gi...@apache.org>.
codelipenghui commented on issue #9092:
URL: https://github.com/apache/pulsar/issues/9092#issuecomment-770235533
@lichuan6 Close this issue first, feel free to reopen it if needed.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org