Hello k6 community! I have been dabbling in k6 as we are investigating its abilities to become our new primary performance testing tool. So far the tool has performed pretty spectacularly! I’ve done most of the leg work to get it up and running and really only have one issue remaining. When running with anything more than 200 VUs on a single node, we’re getting the following error: 413 Request Entity Too Large. Needless to say we’re missing out on metrics when viewing the results in Grafana. I’ve taken a look at another forum post with the same issue: 413 error when writing data to InfluxDB. I tried Ned’s proposed solution of setting max-body-size. But as Ned noted might be the case, this did not seem to actually work for us, as we’re still getting the error and we’ve confirmed that the config is actually set on the influx server. This is pretty much blocking us, as if we can’t review the results of the test, then it’s not going to do us much good.
I have two questions:
- Does anyone have any further suggestions on remediating this issue?
- Has anyone been able to pump significant load to InfluxDB? I’m kind of surprised that this isn’t more commonly discussed, which leads me to believe that I just have something improperly configured.
Error message:
level=error msg="InfluxDB: Couldn't write stats" error="<html>\r\n<head><title>413 Request Entity Too Large</title></head>\r\n<body>\r\n<center><h1>413 Request Entity Too Large</h1></center>\r\n<hr><center>nginx/1.15.5</center>\r\n</body>\r\n</html>\r\n"
I’m going to give UDP connections a shot to see if that might solve this issue. Appreciate any suggestions or help on this!
. Since