Request timed out Error - Influx DB

[Shashank]

I am trying to write Streaming  data from Kafka to Influx DB and at some point I am getting the following error

error:

{message: 'Error: Request time out',

source:

{id: '2abd...c91b42',

type: 'influxdb out',

name: 'Influx'

count: 1},

stack: 'Error Request timed out at ServiceNotavailableError'... Socket. emitRequestTimeout.

I have tried using batcher node but this is combining the documents which is not giving the proper outcome in influxDB. How can I resolve this issue?

Thx

[Colin Law]

Does it carry on after that or is it fatal?

I believe that error means that the node cannot access influx.  Is your influx db on the same machine as node red or is it remote?

Also what hardware and OS are you using?

Colin

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/fb20ba93-54da-4ae2-a153-c4092320519f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Shashank]

It carries but after some time it throws error again. My Node red and Influx are running on different machines.

I am using Centos 7 OS with 16 GB RAM (Where my InfluxDB Server is running).

On Monday, February 12, 2018 at 10:46:52 PM UTC+5:30, Colin Law wrote:

Does it carry on after that or is it fatal?

I believe that error means that the node cannot access influx.  Is your influx db on the same machine as node red or is it remote?

Also what hardware and OS are you using?

Colin

On 12 February 2018 at 15:27, Shashank <shashank...@gmail.com> wrote:

I am trying to write Streaming  data from Kafka to Influx DB and at some point I am getting the following error

error:

{message: 'Error: Request time out',

source:

{id: '2abd...c91b42',

type: 'influxdb out',

name: 'Influx'

count: 1},

stack: 'Error Request timed out at ServiceNotavailableError'... Socket. emitRequestTimeout.

I have tried using batcher node but this is combining the documents which is not giving the proper outcome in influxDB. How can I resolve this issue?

Thx

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

[Colin Law]

On 12 February 2018 at 18:17, Shashank <shashank...@gmail.com> wrote:

It carries but after some time it throws error again. My Node red and Influx are running on different machines.

I have never done that, I run influx and node-red on an Ubuntu machine (in addition to node red running on various other machines, mostly pis) and subscribed to MQTT servers on the pis from node-red to get the data to feed it influx.  I am not suggesting that your technique should not work, just saying it is not the way I do it.

 

Presumably for some reason influx is taking to long to respond across the network, though why that should happen if all else is ok I don't know.

I am using Centos 7 OS with 16 GB RAM (Where my InfluxDB Server is running).

What are you running the instance of node-red that is passing the data to the Centos machine on?

Colin

 

[Shashank]

Even my Node-RED instance is running on Centos 7 but my both machines are within the same network.

Is there a way I can handle this scenario using batcher or InfluxDB batch?