yaron
September 22, 2021, 2:10pm
1
Hi,
We use the Node SDK:
Any clue on what could be the issue?
nadine
September 22, 2021, 3:09pm
2
HI @yaron ,
Thanks for reporting this- let me investigate.
–n
1 Like
nadine
September 22, 2021, 5:42pm
3
hey @yaron - we are still investigating-- please give us some more time to see what the possible underlying issues are.
nadine
September 22, 2021, 6:32pm
4
Hey @yaron ,
On our side, we’re not noticing any connection issues. One of our product engineers recommended using Axios helped with high connection rates with lots of write. You can provide a custom fetch function that overrides the default:
/**
* This file shows how to integrate custom fetch functionality into the rockset fetch api.
* We use axios in this example, and re-use shared HTTP connections instead of creating new
* connections on every request. Useful for conserving connections for high-throughput actions,
* such as writing documents to collections at a high rate.
*/
import rockset from '..';
// import rockset from "@rockset/client"; // replace above line if using outside repo
import axios from "axios";
import * as HttpAgent from "agentkeepalive";
// Configure
const basePath = process.env.ROCKSET_HOST || 'https://api.rs2.usw2.rockset.com';
const apikey = process.env.ROCKSET_APIKEY as string;
const { HttpsAgent } = HttpAgent;
// create axios instance with agentkeepalive -- re-use shared session when
// possible instead of creating new sessions on each request.
show original
Let me know if this helps, please update us if this solves the errors you are seeing.
Best,
nadine
September 23, 2021, 8:41pm
5
Hey @yaron !
Touching base here. Please let me know if this helped.
