# BulkProcessor 'bulk' operation for indexing **URL:** \ **Category:** Elasticsearch\ **Created:** [October 17, 2017, 5:00am UTC](https://discuss.elastic.co/t/bulkprocessor-bulk-operation-for-indexing/104169 "2017-10-17T05:00:45Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![pokaleshrey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pokaleshrey/32/48680_2.png) [@pokaleshrey](https://discuss.elastic.co/u/pokaleshrey)\ **Post date:** [October 17, 2017, 5:00am UTC](https://discuss.elastic.co/t/bulkprocessor-bulk-operation-for-indexing/104169/1 "2017-10-17T05:00:45Z")
Version: 5.6.2 We are trying to use BulkProcessor (Async) for indexing, the operation has millions of documents. On the application client side we are using High Level REST Client and ThreadPool. We are able to generate a high amount of load, _for eg lets assume 30threads in bulkActionSize=500_. On ES side, lets assume i have only one master node with 5shards and 0 replicas. Machine is a Octa-Core machine * * * **Question:** - While setting thread pool we can set the executor. We have set it to 'Names.BULK'. ES documentation says, by default this type of operation will use _FixedExecutorBuilder_. This operation will use fixed number of threads on ES side. What will happen if we do the bulk indexing using Names.GENERIC which has _ScalingExecutorBuilder_, to achieve scaling ?? This can give us more threads to index. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 14, 2017, 5:01am UTC](https://discuss.elastic.co/t/bulkprocessor-bulk-operation-for-indexing/104169/2 "2017-11-14T05:01:17Z")
Closed on November 14, 2017, 5:01am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.