# Duplication Due to rollover policy in kibana,data coming from logstash pipeline **URL:** \ **Category:** Logstash\ **Created:** [November 28, 2022, 3:19pm UTC](https://discuss.elastic.co/t/duplication-due-to-rollover-policy-in-kibana-data-coming-from-logstash-pipeline/319959 "2022-11-28T15:19:55Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![PRASHANT\_MEHTA](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prashant_mehta/32/101764_2.png) [@PRASHANT\_MEHTA](https://discuss.elastic.co/u/PRASHANT_MEHTA)\ **Post date:** [December 1, 2022, 2:52pm UTC](https://discuss.elastic.co/t/duplication-due-to-rollover-policy-in-kibana-data-coming-from-logstash-pipeline/319959/8 "2022-12-01T14:52:55Z")
@gbrown I read your this post and you suggessted one solution,I'm not sure how this can be done. How can this be configured in logstash pipeline,updates happens in rollover index and only new documents comes in present index. > [@Indice rollower](https://discuss.elastic.co/t/indice-rollower/194448): > > during the rollover - we notice the document count is already in the old index and when updating during that second the document count gets to the newly created indice as well. is there any way to prevent the duplication of data during the rollover ? --- _[View the full topic](https://discuss.elastic.co/t/duplication-due-to-rollover-policy-in-kibana-data-coming-from-logstash-pipeline/319959)._