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

Investigate connection-to-server limit (if any) in node connector, implement if inadequate #83

Open
jonvuri opened this issue Jun 2, 2018 · 3 comments
Assignees
Labels
tracked-in-jira Issue is being tracked in Jira, link mentioned in issue comments

Comments

@jonvuri
Copy link
Contributor

jonvuri commented Jun 2, 2018

Limit number of connections to server to around 6 like browsers do in Node mapd-connector, with some task dispatcher such as async.eachLimit. (Possible existing pattern in mapd-client-v2)

@heavyai heavyai deleted a comment from esamuel1 Jun 12, 2018
@esamuel1
Copy link

Adding notes for the fix that helped resolve this:

Add the following line to this file: /lib/systemd/system/mapd_web_server.service?
LimitNOFILE=65536

This needs to go between ExecStart and Restart properties in the file. I After editing the file, you will need to run the below command for the changes to pick up:

sudo systemctl daemon-reload && sudo systemctl restart mapd_web_server

@niviksha
Copy link

@chrisv can you please track this for 4.0.1 prioritization? thanks!

@niviksha niviksha assigned biovisualize and unassigned jonvuri Jun 12, 2018
@jonvuri
Copy link
Contributor Author

jonvuri commented Apr 1, 2019

Tracking in https://jira.omnisci.com/browse/FE-8234

@jonvuri jonvuri added the tracked-in-jira Issue is being tracked in Jira, link mentioned in issue comments label Apr 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tracked-in-jira Issue is being tracked in Jira, link mentioned in issue comments
Projects
None yet
Development

No branches or pull requests

4 participants