Skip to content

Documents lost in Consumer during target Solr restart.#73

Closed
sigram wants to merge 1 commit intoapache:mainfrom
lucidworks:2640-consumer-recovery
Closed

Documents lost in Consumer during target Solr restart.#73
sigram wants to merge 1 commit intoapache:mainfrom
lucidworks:2640-consumer-recovery

Conversation

@sigram
Copy link
Contributor

@sigram sigram commented Sep 22, 2023

This modified test illustrates a scenario when target Solr node(s) go missing (for example due to a crash, a forced restart, or connectivity issues) BUT at the same time the Zookeeper remains online.

The test fails because it looks like some of the documents are lost by the Consumer, even though the failed_resubmit code path should resubmit them back to Kafka and they should be picked up later when Solr is back online.

@markrmiller
Copy link
Member

Taking a look.

@markrmiller
Copy link
Member

Good catch, big hole that that test only tests dropping zk and not Solr.

I'm just wrapping up a fix.

Appears to be caused by batching multiple Kafka records to a SolrRequest to send to Solr, but on failure, adding back just the last Kafka record, so of course you loose the previous records in the batch.

@sigram
Copy link
Contributor Author

sigram commented Oct 13, 2023

If I'm not mistaken this has been fixed in PR 75? if so then this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants