-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the max data size which can be processed by netdata-timescale-relay? #3
Comments
Hmm, good question. There shouldn't be a practical limit, it just reads until the stream stops. I currently can't replicate this locally, so some more information is appreciated. My local tests, having no netdata matching filter, puts a metrics row at about 14k. A filtered one is 3k (or so). Yours is 2 megs or so -- share your conf with me ([email protected] if you'd like to do it privately) - I'm interested in how you have a 2MB sample as a routine send, wow. Some public questions:
In the meantime I'll work up a test scenario that just injects N bytes of data straight to the relay and see how it does. Thanks. |
Exporting conf of parent node:
Stream conf of child node:
All child nodes and parent node are collecting all mtrics at 1Hz.
|
I reproced it. Error log of netdata:
And there is log of netdata-timescale-relay:
|
Here is my problem.
When I export metrics from metrics at every 1s (as collected) from parent node and there is one child node, I get error from netdata like
2021-01-18 17:20:31: netdata ERROR : MAIN : EXPORTING: failed to write data to 'localhost:14866'. Willing to write 2092079 bytes, wrote 1766662 bytes. Will re-connect. (errno 11, Resource temporarily unavailable)
.When I add filter
send charts matching = !cpu.cpu* !ipv6* !users.* nfs.rpc net.* net_drops.* net_packets.* !system.interrupts* system.* disk.* disk_space.* disk_ops.* mem.*
, it works well.So I guess the error is raised by data size. There is too much data exporting to timescaledb through netdata-timescale-relay.
Am I right?
If yes, what is the max data flow that netdata-timescale-relay can handle?
The text was updated successfully, but these errors were encountered: