It's not very clear that calling getWriteApi unnecessarily (e.g in a repeated loop) is a bad idea when really, it is as a new thread will be created each time (a RxNewThreadScheduler). Only recently noticed this in my project when I ran a thread dump and I had over 1k threads.

Just to put some abusive cases as examples:

• https://github.com/donghoon-khan/kubernetes-demo/blob/master/app/spring-influx2/src/main/java/com/donghoon/khan/influxdemo/repository/TemperatureRepository.java
• (not a functioning project but still a mistake made considering it would be run as a cronjob) https://github.com/Ccccx/cloud/blob/master/influxdb/src/main/java/com/example/influxdb/task/DemoTask.java
• From what I can tell here, a new one would be made every 5 seconds https://github.com/Iniuriarum/Iniuriarum/blob/master/src/main/java/com/remcobuddelmeijer/influxdb/local/LocalInfluxDBRepository.java

Basically, it's a mistake people are making and it's not evident until you have the issue (and have actually realised you've got the issue) and have to guess where the threads are coming from.