# Concurrency command as in Splunk **URL:** \ **Category:** Kibana\ **Created:** [June 18, 2020, 7:11am UTC](https://discuss.elastic.co/t/concurrency-command-as-in-splunk/237579 "2020-06-18T07:11:28Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![akh](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@akh](https://discuss.elastic.co/u/akh)\ **Post date:** [June 18, 2020, 7:11am UTC](https://discuss.elastic.co/t/concurrency-command-as-in-splunk/237579/1 "2020-06-18T07:11:28Z")
Hi, Is there a way to implement the concurrency command as in Splunk? We need to take into consideration the processes that started earlier but are still in progress during the current second. Is it possible to do so? ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [July 13, 2020, 5:48am UTC](https://discuss.elastic.co/t/concurrency-command-as-in-splunk/237579/2 "2020-07-13T05:48:12Z")
> [@akh](#): > > d as in Splunk? > We need to take into consideration the processes that started earlier but are still in progress during the current second. Is it possible to do so? HI are you trying this ? [Optimistic concurrency control | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/optimistic-concurrency-control.html) Hope this helps Thanks Rashmi ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 10, 2020, 5:48am UTC](https://discuss.elastic.co/t/concurrency-command-as-in-splunk/237579/3 "2020-08-10T05:48:15Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.