Closed paul-snively closed 8 months ago
I have to apologize. I meant fs2-kafka 2.2.0. :-)
This happens because deleteTopic
might complete before the change has propagated to all brokers, see here. I'm not sure if there's more that can be done except to retry the creation.
I think we could add something about this to the scaladoc.
Since KafkaFuture
now uses CompletionStage
, this should be fixed.
I think it's safe to close this 2 year old issue.
In fs2-kafka 1.0.3, when I try to use
deleteTopic
on theAdminApiClient
and thencreateTopic
, nondeterministically I will get a failed effect indicating that the topic already exists, i.e. hasn't been deleted by the timedeleteTopic
passes control to the next effect. Looking at the code, this suggests to me that the machinery for supportingcancelable
, which apparently lifts aKafkaFuture
to theF
context with anAsync
constraint, is not working correctly (which frankly seems understandable, sinceKafkaFuture
is apparently its own wild-west thing).