Donot create transaction components for function work topic#11543
Donot create transaction components for function work topic#11543liangyepianzhou wants to merge 10 commits into
Conversation
| try { | ||
| workerConfig = WorkerConfig.load(fnWorkerConfigFile); | ||
| } catch (IOException e) { | ||
| e.printStackTrace(); |
There was a problem hiding this comment.
please handle the exception not print it
| Assert.isNonEmpty(workerConfig); | ||
| Assert.isNonEmpty(topic); |
There was a problem hiding this comment.
Don't we need to handle the returned value?
| } | ||
| transactionBuffer.syncMaxReadPositionForNormalPublish((PositionImpl) ledger.getLastConfirmedEntry()); | ||
| } | ||
| private boolean checkTopicIsFunctionWorkerService(PersistentTopic topic){ |
There was a problem hiding this comment.
We'd better find a common place to avoid the method duplicate
| IS_FENCED_UPDATER.set(this, FALSE); | ||
| } | ||
| private boolean checkTopicIsFunctionWorkerService(PersistentTopic topic){ | ||
| String fnWorkerConfigFile = |
There was a problem hiding this comment.
The function work config file may be in a different place, user can define it with environment variable
|
/pulsarbot run-failure-checks |
| WorkerConfig workerConfig = topic.getBrokerService().getPulsar().getWorkerConfig().get(); | ||
| String topicName = topic.getName(); | ||
| return workerConfig.getClusterCoordinationTopic().equals(topicName) | ||
| || workerConfig.getFunctionAssignmentTopic().equals(topicName) | ||
| || workerConfig.getFunctionMetadataTopic().equals(topicName); |
There was a problem hiding this comment.
This can only work for the broker run with the function worker? If the function working running independently, here will get an incorrect worker config.
I think we already have a PR to support transaction buffer and pending ack lazy creation, if new transactions happens on a topic, the transaction buffer and the pending ack will not be created?
4 participants
Fixes #11481
Motivation
Modifications
Verifying this change
Add
TransactionTest::testFilterFunctionTopicForTransactionComponentto verifyDoes this pull request potentially affect one of the following parts:
If
yeswas chosen, please highlight the changesDocumentation
For this PR, we don't need to update docs.