-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
sql: zero SQL mem pool on OpenBSD prevents clients from connecting #15836
Comments
This is the line that proves
On a working
I think you can work around this by specifying manually Also since |
Can you try this out and report your results? |
@mrijkeboer I also filed #15839. If you feel like it a contribution to fix that issue would be welcome! |
@knz when I add On a similar note, I also see the following in my log (probably also
With regards to #15839, I have never programmed in Go and I'm currently on a very tight schedule, so I don't have the time available to dive into Go. |
The issue with file descriptors is a separate issue, I haven't looked into that. There are two mechanisms (one more next to gosigar) for managing the file descriptors, perhaps both need tweaking. Thanks for reporting the issue anyway. I'm glad the workaround helped! |
@knz Do you want me to open a github issue for the file descriptor issue? |
@knz What would be recommended values (% of main memory) for |
Please file a separate issue for the file descriptor issue, and mention there how you had to adjust with sysctl to get it working. The defaults for |
This is obsoleted by #18040. |
BUG REPORT
When I try to connect to a cluster that is running on OpenBSD I get the following error:
The cluster is started with the following command:
Headers of most recent log file:
On the Cockroach forum @knz asked me to run the cluster with the
--vmodule=mem_usage=2
option and provide the output:The text was updated successfully, but these errors were encountered: