LevelDB storage engine
(MDEV-3841)
|
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Technical task | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Sergei Petrunia |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | leveldb | ||
| Issue Links: |
|
||||
| Description |
|
LevelDB uses the global value of leveldb_lock_wait_timeout, but ignores the session one.
Output shows that the timeout is 2 seconds, not 5:
Here is a tiny modification to leveldb.test which also shows the problem (unfortunately, I don't see a better way than sleep):
This part of the test sets the session timeout to 1000 seconds, starts an update, then switches to the connection which holds the lock and releases it. Then it returns to the first connection and checks that the update worked. However, there is no delay anywhere in the process, the operations are fast and well within 1 second, so the test doesn't really check that the timeout value affects the outcome. With the delay, the test starts failing with ER_LOCK_WAIT_TIMEOUT at line 357, which is not supposed to happen.
|