Bug: Log is flooded with RequestTimedOutErrors about node-red-contrib-influxdb HOT 8 OPEN

After playing a little bit with node-red & influxdb I get now this (slightly different) error:

from node-red-contrib-influxdb.

Hi,
I have the same problem like winnieXY.
I´m also using V0.7.0
I'd triggered a couple of http requests with one inject node and want to transfer the result to influxdb.
In order to strech the requests at the same time, i´ve mulitplied the injects and start each with a time shift of 0,2 s; but, the same result.
A restart of node red helps for a handfull of hours.
NodeRed and influxdb runing in a docker container on a synology with more than enough memory and are both up to date.
If you need more information feel free to contact me.

from node-red-contrib-influxdb.

Any news on that? That's really a showstopper right now

from node-red-contrib-influxdb.

I think i don't have an solution.
But... Do you use influx 2 with flux-query oder with influx 1 and the older query language?

And do you use it in docker or as native installation?

from node-red-contrib-influxdb.

from node-red-contrib-influxdb.

Hi,
yesterday i´ve had again the problem with the RequestTimedOutErrors.
My oberservation: 1st i´ve tried to transfer msg.payload as an array (i.e. msg.measurement = "power"; msg.payload =[{value: #}, {phase: "ph0"}, {level: "basement"}];
(you can transfer to influx not only the meassurement and the value, you can also add attributes to the measurement).
Here I´ve got the errors.
When I reduce the #of attributes to one, the node works without errors.
(i.e. msg.measurement = "powerPhase0"; msg.payload =[{value: #}, {level: "basement"}];
or even a plain value in the payload and measurement="PowerPhase0Basement".
Maybe it´s a hint to solve the problem or to create a workaround
BR

from node-red-contrib-influxdb.