2020-03-23 09:23:14 UTC - xue: Run Functions-worker separately,Configure 
Proxies for 
like this,Port that discovery service listen on 8082,  then start pulsar 
proxy,but curl <http://hostname:8082/admin/v2/worker/cluster>
2020-03-23 09:24:37 UTC - xue: 
2020-03-23 09:25:14 UTC - xue: {"reason":"Function worker service is not done 
initializing. Please try again in a little while."}
2020-03-23 09:52:15 UTC - hhiroshell: @hhiroshell has joined the channel
2020-03-23 10:01:22 UTC - sbourke: Hi, does anyone know if swagger.json is 
served locally by the admin web service, and if so the path it's located at?
2020-03-23 10:03:10 UTC - Ron Farkash: @Ron Farkash has joined the channel
2020-03-23 10:08:38 UTC - Ron Farkash: As an administrator I would like to 
limit my clients' produce/consume rate, I found it a bit hard to understand 
from the documentation on how I would go about doing that. Could someone 
provide me with a clear explaination on what are Pulsar's capabilities when it 
comes to controlling quota as an admin (when my producers and consumers are not 
directly under my control and I wouldn't want them to deplete my resources)?
2020-03-23 12:07:54 UTC - Horacio Gonzalez: @Horacio Gonzalez has joined the 
2020-03-23 12:15:57 UTC - Konstantinos Papalias: what's the new structure 
@Dennis Yung, just curious while developing on a previous version, still try to 
understand the changes required for 2.5.0 (if any)
2020-03-23 14:06:48 UTC - Ming: There are dozen throttling parameters 
2020-03-23 16:15:25 UTC - Ron Farkash: @Ming is it possible even per 
2020-03-23 20:05:37 UTC - Alex Yaroslavsky: Hi, is it possible to use functions 
with encryption? From the function API it doesn't seem to be possible or am I 
missing something?. I don't even need the function to decrypt the data, just 
forward it as is to a different topic.
2020-03-23 20:35:30 UTC - Aaron Stockton: so does acking a message on an 
exclusive / failover subscription have any affect?
2020-03-23 21:03:45 UTC - tcourdy: quick question.  when using k8s runtime for 
functions are the logs of the functions still stored in the broker pod?
2020-03-23 21:06:06 UTC - chris: with the k8s runtime logs go to stdout on the 
function pods
2020-03-23 21:09:30 UTC - tcourdy: so can that be configured to be routed to 
the broker pods via the `functions_worker.yaml` somehow 
  Otherwise I imagine those logs will be ephemeral?
2020-03-23 21:15:00 UTC - tcourdy: or maybe its sounding like if i want 
persistent logs the best approach is to modify my functions to write the log 
output to a log topic and then having something else consume that and write it 
to somewhere persistent? 
2020-03-23 21:15:44 UTC - chris: that is one option. also the pods logs are 
around on the host far a while as long as the pod is running
2020-03-23 21:16:17 UTC - chris: also we had success using this 
2020-03-24 00:55:35 UTC - David Kjerrumgaard: If you have a function that 
returns a type, e.g. `implements Function&lt;POJO1, POJO2&gt;` is there a way 
to include some properties in the response record?  Or should I do something 
like the following? `ctx.newOutputMessage(creditCardTopic, 
2020-03-24 01:36:09 UTC - tuteng: hi, Have you changed the parameter username? 
in our initialization environment, this parameter is the same as that of 
database initialization and cannot be modified. `docker run -it -p 9527:9527 -e 
DRIVER_CLASS_NAME=org.postgresql.Driver -e 
URL='jdbc:<postgresql://>' -e USERNAME=pulsar -e 
PASSWORD=pulsar -e LOG_LEVEL=DEBUG -v $PWD:/data 
apachepulsar/pulsar-manager:v0.1.0 /bin/sh`
2020-03-24 01:37:58 UTC - tuteng: The current user name and password are 
configured to connect to the database. The current default user name and 
password are pulsar and pulsar.
2020-03-24 01:38:10 UTC - tuteng: @Pradeesh
2020-03-24 02:57:12 UTC - Dennis Yung: instead of commenting out each untime 
env options, there is a new functionRuntimeFactoryClassName param, with configs 
for each runtime grouped under functionRuntimeFactoryConfigs
2020-03-24 06:41:06 UTC - Abhilash Mandaliya: hi
I have developed my own sink connector and it is working fine. But it is not 
working on 2 pulsar brokers. I am running create command on 1st node like below 
which works fine and runs the connector.
```pulsar-admin sinks create \
    --tenant public \
    --namespace default \
    --name my-sink \
    --sink-type my-sink-type \
    --inputs players \
    --sink-config-file my-sink-connector-config.yml```
But on the second node, I am trying to run start command to start my sink 

```pulsar-admin sinks start \
--tenant public \
--namespace default \
--name my-sink```
It doesn’t start and gives the error:

*Operation not permitted*

*Reason: Operation not permitted*

Can anyone help here?

Reply via email to