Database breaking randomly
See original GitHub issue- EdgeDB Version: 1.0-alpha.2+g16f75ece5.d20200122
- OS Version: Running in docker - Host unbuntu 19.10
Steps to Reproduce:
Cannot say, it produced randomly with a database that was working well. The db broke, the js client returned this error:
code: 16777216
message: "cannot issue new command"
type: "InternalServerError"
Stoping a restarting the docker instance solved the issue.
Please let me know how I can provide more details if it occurs again
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Database Host Server Connections Drop after a Period ... - IBM
Network hardware causes connection drops after a period of inactivity. The disconnects might be prevented with changes to hardware settings ...
Read more >Ten Common Database Design Mistakes - Simple Talk
In a database, the process of normalization, as a means of breaking down and isolating data, takes every table to the point where...
Read more >Why am i getting these random timeout errors on mysql ...
I wonder if having two database connections is breaking things or having two applications define the same connection is breaking things ...
Read more >Accidentally destroyed production database on first day of a ...
I had issues with HDDs randomly failing when I was growing up (3 separate ... "If an intern can break production on their...
Read more >How to Break an Existing Single Database File Into Multiple ...
See how to break up a single data file into multiple data files so that they can be spread over ... Use the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Reproduced this as well. Agree with @elvis that this looks like a duplicate of #1314.
This seems to be a problem specific to HTTP ports: #1314