Timeout error in CLI and internal server error in Node-RED while writing data but the data is still written

influxdb
#1

Hello,

I am running Influx 1.7.6 on Ubuntu 16.04. I am using tsi1 and have wal-fsync-delay = “0.05s” in my config file. I am running the ubuntu as a virtual server on my physical ubuntu server and writing to the database on a RAID 6 array with spinning disks. It is probably of note that I am sporadically getting high IO usage as observed with various Ubuntu utilities that show influxd as the culprit and it hangs my system. It is sometimes so bad that just in the terminal running a command like “ls” takes many seconds to run. However, all my data appears to be writing! I am doing pretty minimal writes, generally 1 write every 30 seconds or so.

Mostly, I am writing data from Node-RED to influx and seemingly randomly get generic internal server errors (as shown in Node-RED debug panel) after writing data. However I have checked, and data is definitely written to influx. Then today I did my first inserts of data using the CLI to modify a data value and I got a timeout error but the data was definitely written. See below for the CLI output where it shows the timeout error but you can see the value 769.92168 has now changed to 0, just as I intended. Is there anything I can do to eliminate this error, or is it really a problem? The fact that my system is routinely swamped by IO does not seem to be good either.

select “chargeCap”::field FROM “cellCycleStats” WHERE “cellName” = ‘190427_quad_cop_ch1’ ORDER BY time DESC LIMIT 10
name: cellCycleStats
time chargeCap


1556474802868510342 8.486957
1556473986095508441 769.92168

insert cellCycleStats,cellName=190427_quad_cop_ch1 chargeCap=0 1556473986095508441
ERR: {“error”:“timeout”}

select “chargeCap”::field FROM “cellCycleStats” WHERE “cellName” = ‘190427_quad_cop_ch1’ ORDER BY time DESC LIMIT 10
name: cellCycleStats
time chargeCap


1556474802868510342 8.486957
1556473986095508441 0