Gatsby-Lee opened a new issue #4748: URL: https://github.com/apache/hudi/issues/4748
Hi, I am leaving my question here since I don't know where to put this type of question. I also googled the question I have, but I couldn't find one. Please let me know where I should put this type of question next time. My question is related to Hudi write. **Context** - Hudi version: 0.9 ( running in AWS Glue 3 ) - using Hudi Metadata table ``` "hoodie.metadata.enable": "true" ``` - using SINGLE_WRITER ``` "hoodie.cleaner.policy.failed.writes": "EAGER" "hoodie.write.concurrency.mode": "SINGLE_WRITER" ``` - using zookeeper as lock provider ``` "hoodie.write.lock.provider": "org.apache.hudi.client.transaction.lock.ZookeeperBasedLockProvider", "hoodie.write.lock.zookeeper.port": port, "hoodie.write.lock.zookeeper.url": zookeeper_url "hoodie.write.lock.zookeeper.base_path": "/hudi_write_lock", "hoodie.write.lock.zookeeper.lock_key": table_name, ``` I setup the zookeeper as lock provider to use Hudi Metadata table with async Hudi service. https://hudi.apache.org/docs/metadata/ **Question:** Even if hoodie.write.concurrency.mode=SINGLE_WRITER, do the Hudi table services ( cleaner, compaction, clustering ) + Hudi write use the provided zoopkeeper lock? Somehow, I keep seeing FileNotFoundException issue when Hudi tries to access files based on Hudi Metadata. Therefore, I am investigating what makes Hudi Metadata out-dated. Thank you -- 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]
