[MDEV-14220] (draft) set global rocksdb_pause_background_work=1 freezes Created: 2017-10-30 Updated: 2018-04-12 Resolved: 2018-04-12 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - RocksDB |
| Affects Version/s: | 10.2.9 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrii Nikitin (Inactive) | Assignee: | Sergei Petrunia |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
setting rocksdb_pause_background_work=1 freezes server During load test of MDEV-14047 with script below:
I tried to execute `set global rocksdb_pause_background_work=1` in parallel connection, which was just hanging for minutes. I tried Ctrl+C, `set global rocksdb_pause_background_work=0` in another connection - it was hanging for some time more, then server resumed. Stats below from the script output indicate period of hanging, which started after "Uptime: 2413" :
|
| Comments |
| Comment by Elena Stepanova [ 2018-01-27 ] |
|
Tried to reproduce, couldn't so far. |
| Comment by Sergei Petrunia [ 2018-04-12 ] |
|
Perhaps rocksdb_pause_background_work=1 also pauses compaction... if it does, RocksDB will eventually slow down and then freeze the write operations, because it will not let compaction fall too far behind. This doesn't explain why you were not able to reproduce, though... As far as I know, rocksdb_pause_background_work is not practically useful for production scenarios. Its use case is debugging/testing where one does not want race conditions with background jobs. |