-
Notifications
You must be signed in to change notification settings - Fork 1k
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 opening views: badmatch/ badarg, ets member mem3_openers #1106
Comments
Do you get the exact same error on every node, or does the shard in the error line change? |
It is the exact same shard when error appears in other nodes. |
How can I check if everything is OK with the shard (shards/50000000-5fffffff/_users.1510390507)? |
Try replicating the If this works, you could try scheduling a maintenance window, deleting |
I also having the similar errors couchdb2.1
This happens every time I start couchdb with command |
@tarasvaskiv It's definitely ready for production - it's in use in tens of thousands of installations world wide that I know of, personally. And I'm just one person. We do need to fix this problem, though. Reopening. |
_auth
"
Got a similar issue
It happened when I changed the settings values of the auth Please fix. For the meantime, is there any way to undo the changes? |
@ThibaultJanBeyer Not fixing this issue, but you can revert that change by editing your |
Yes, that did resolve the problem. However, generally wrong values should not be permitted to enter in the UI or at least not cause a total crash. Thanks for the Help! |
Seeing this too:
Doesn't seem to affect functionality though. |
@davedoesdev what q value do you have configured? |
reflecting on this: we’d need a lot more info on this in terms of system setup, cluster config, load on couch, potential other load on machines, network etc. I’ll close this until we have a report with a more complete set of reproducible steps. |
Trying to add some more information here since I have similar errors in my log (actually a lot of them):
Usually those errors are preceded by lines like these:
I also noticed that the stat Other info:
The same application and database configuration (but with different data) is running on another environment, actually with higher load and many more databases and I can't see all those error messages. |
We have a 6-node cluster configured with q=16.
Every time we restart the server, couchdb logs same errors on startup.
Expected Behavior
It should start without errors
Current Behavior
It starts with errors:
Possible Solution
I do not know-
Configuration
We use default settings except:
local.ini
vm.args
sys.config
Environment
Software is running on virtualized Centos 7 using OpenVZ 7.
Each node has same configuration.
Each node has 16 cores.
The text was updated successfully, but these errors were encountered: