-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[BUG] miniob crashes when concurrently creating tables #355
Comments
It seems that there is data race when concurrently creating table. |
MiniOB doesn't support creating tables or indexes concurrent. You must control it manually. |
okk, can you give me some hints about the solution. |
There are two points:
It's easy to resolve the first problem. We can just add a Usually, we use different locking mode for thus operations.
Below is the locking compatible table:
As you can see, when you just want to visit the records of the table, you should get the
Before we want to do some actions, we should get the specific mode of lock. You can use some other solutions as the table locking is a little complex. But please share your idea with me before you submit the Pull Request. If you can complete this feature, I'd like to propose you to be the miniob committer. Thanks. |
Are there any blogs or paper that introduce the implemention of the online index? |
Sure, here it is innodb intention locks and some other pages: SQL server: https://sqlundercover.com/2019/07/25/intent-locks-in-sql-server/ PostgreSQL: https://habr.com/en/companies/postgrespro/articles/500714/ ARIES: A Transaction Recovery Method Supporting Fine-Granularity Locking and Partial Rollbacks Using Write-Ahead Logging |
get it |
This is a simple design doc, many things may not be considered or described. Hope for your suggestions, I will improve it. PTAL. @hnwyllmm |
Sorry that I response your message so late. I have read your document and I list the comments below in Chinese.
如果有兴趣可以加我微信(hnwyllmm_126),我们可以在miniob开发群中大家一起讨论。 |
好的 我会做相应修改 |
Describe the bug
A clear and concise description of what the bug is.
** Environment**
Environment Details sometimes important
Fast Reproduce Steps(Required)
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
no crash
Actual Behavior
What is the result? picture is allowed
crash
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: