jiangpengcheng opened a new issue, #24720:
URL: https://github.com/apache/pulsar/issues/24720

   ### Search before reporting
   
   - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) 
and found nothing similar.
   
   
   ### Read release policy
   
   - [x] I understand that [unsupported 
versions](https://pulsar.apache.org/contribute/release-policy/#supported-versions)
 don't get bug fixes. I will attempt to reproduce the issue on a supported 
version of Pulsar client and Pulsar broker.
   
   
   ### User environment
   
   broker version: a2b69cc
   
   
   ### Issue Description
   
   The `PulsarMetadataStateStoreProviderImpl.init` requires the `Map<String, 
Object> config` argument contains a `METADATA_STORE_INSTANCE` or a 
`METADATA_URL` field, and this method is called in two places:
   
   - JavaInstanceRunnable.setupStateStore
   - PulsarWorkerService.start
   
   in both places, the passed arguments never put those two fields, which makes 
the `PulsarMetadataStateStoreProviderImpl` cannot be init properly
   
   ### Error messages
   
   ```text
   
   ```
   
   ### Reproducing the issue
   
   1. start pulsar service standalone with config: 
`stateStorageProviderImplementation: 
org.apache.pulsar.functions.instance.state.PulsarMetadataStateStoreProviderImpl`
 in `conf/functions_worker.yml`
   2. create a stateful function:
   
   ```
   pulsar admin functions create --jar 
pulsar-functions/java-examples/target/pulsar-functions-api-examples.jar 
--tenant public --namespace default --name test-word-count-java --classname 
org.apache.pulsar.functions.api.examples.WordCountFunction --inputs 
persistent://public/default/test-java-input-word-count
   ```
   
   ### Additional information
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] I'm willing to submit a PR!


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to