# Point In Time for multi threaded queries / slices

**URL:** <https://discuss.elastic.co/t/point-in-time-for-multi-threaded-queries-slices/316243>\
**Category:** Elasticsearch\
**Tags:** point-in-time\
**Created:** [October 10, 2022, 3:51pm UTC](https://discuss.elastic.co/t/point-in-time-for-multi-threaded-queries-slices/316243 "2022-10-10T15:51:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![str8y](https://avatars.discourse-cdn.com/v4/letter/s/f05b48/32.png) [@str8y](https://discuss.elastic.co/u/str8y)\
**Post date:** [October 10, 2022, 3:51pm UTC](https://discuss.elastic.co/t/point-in-time-for-multi-threaded-queries-slices/316243/1 "2022-10-10T15:51:19Z")

</div>

Hi,

I read in the documentation that every result could contain an updated id for the pit I created, which I have to use in subsequent search requests.

How does that behave in scenarios where I'm using multiple searches with the same PIT in parallel?  
For instance if I use multiple slices to paginate over the whole result set.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 7, 2022, 3:51pm UTC](https://discuss.elastic.co/t/point-in-time-for-multi-threaded-queries-slices/316243/2 "2022-11-07T15:51:51Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
