Skip to content
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

Error: Stream error: 8 RESOURCE_EXHAUSTED: exceeded maximum concurrent bundle result connections limit. too many open connections #54

Open
youngqqcn opened this issue Jan 24, 2025 · 11 comments

Comments

@youngqqcn
Copy link

Error: Stream error: 8 RESOURCE_EXHAUSTED: exceeded maximum concurrent bundle result connections limit. too many open connections

@08e4ccee
Copy link

@youngqqcn have you figured out the solution? or gotten a response from staff on reasoning? I am only subscribing to one bundle result yet get the same error.

@azflin
Copy link

azflin commented Jan 30, 2025

same

@PeterFolsom
Copy link

I experience the same error at first call and i only have one bundle result. Is the error message maybe misleading and the actual error is something else?

@08e4ccee
Copy link

08e4ccee commented Feb 1, 2025

@PeterFolsom I've been using bundle results for 2.5 months with no issues till this and nothing has changed in my code, so I'm not sure what the error could be. my transactions are landing even with the error, but occasionally I get a non landing transaction and have no idea why as I can't get bundle results.

@JingYeoh
Copy link

JingYeoh commented Feb 4, 2025

same issue

@simoncodev
Copy link

same here.

@azflin
Copy link

azflin commented Feb 5, 2025

can the devs do sumfin

@superpdm
Copy link

same issue

@IliaZyrin
Copy link

same

@PeterFolsom
Copy link

@PeterFolsom I've been using bundle results for 2.5 months with no issues till this and nothing has changed in my code, so I'm not sure what the error could be. my transactions are landing even with the error, but occasionally I get a non landing transaction and have no idea why as I can't get bundle results.

I have been able to resolve this by changing the way i bundled. At first i had used code that i found in a youtube video,

const bundle = new jito.bundle.Bundle([tx], 2);
...
jitoClientInstance.onBundleResult(onSuccess, onError);
const bundleUID = await jitoClientInstance.sendBundle(bundle);

now i got it working by adhering to different example code i found for jito:
Cant explain why that works though.

type BundleResponse = Result<string, SearcherClientError>;
const results: BundleResponse[] = await Promise.all(
bundles.map(async b => {
try {
const resp = await c.sendBundle(b);
if (!resp.ok) {
return resp;
}
console.log('resp:', resp.value);
return resp;
} catch (e) {
console.error('error sending bundle:', e);
return {
ok: false,
error: e as SearcherClientError
};
}
})
);

So maybe try to change your code a bit, and see if that works,

@roguzh
Copy link

roguzh commented Feb 22, 2025

I am also experiencing the same issue. Nothing has changed since a while but this just started occurring out of nowhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants