# Anonymous CompletableFuture threads with burstable pods

DevFeed: [Anonymous CompletableFuture threads with burstable pods](<https://devfeed.tech/articles/anonymous-completablefuture-threads-with-burstable-pods-26081.md>)

Original publisher: [Read original article](<https://blog.arkey.fr/2020/12/11/completablefuture-with-burstable-pods/>)

Author: brice.dutheil@gmail.com (Brice Dutheil)

Published: 2020-12-11T13:05:00Z

Content type: article

Language: en

Sources: [The Coffee Workshop](<https://devfeed.tech/sources/the-coffee-workshop.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Concurrent Programming](<https://devfeed.tech/topics/concurrent-programming.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>)

Tags: [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [container](<https://devfeed.tech/tags/container.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [java](<https://devfeed.tech/tags/java.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [parallelism](<https://devfeed.tech/tags/parallelism.md>), [threads](<https://devfeed.tech/tags/threads.md>)

## AI overview

This article investigates why CompletableFuture can create many short-lived anonymous threads when running in a container with limited processor visibility. It traces the behavior to the default ForkJoinPool and discusses configuring an executor or overriding the pool parallelism.

## Source excerpt

It all started when opening a JFR recording, I noticed a very large and growing number of very short lived threads.