[SERVER-28798] Verify process stops logging after EBUSY. Created: 14/Apr/17 Updated: 27/Oct/23 Resolved: 14/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.3 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Andrey Kostin | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 16.04 x64 |
||
| Participants: |
| Description |
|
After EBUSY reported verify progress is not being logged. However other db actions are logging as usual.
Nothing more in logs until validation completed. Is it expected behavior? |
| Comments |
| Comment by Eric Milkie [ 14/Apr/17 ] |
|
That's correct. |
| Comment by Andrey Kostin [ 14/Apr/17 ] |
|
Understood. This is the last line for verify process, the validation process doesn't log anything until the end. |
| Comment by Eric Milkie [ 14/Apr/17 ] |
|
I think the behavior you describe is what always happens, regardless of whether verify() returns EBUSY or not. After the call to WiredTiger's verifyTable() returns, the validate code then does a collection scan. The progress messages only appear while verifyTable() is running within WiredTiger. The code doesn't appear to log any progress while it is doing the collection scan. See WiredTigerRecordStore::validate(). |
| Comment by Andrey Kostin [ 14/Apr/17 ] |
|
No, I'm not talking about the warning itself but the fact that it continues to validate without any new log messages. |
| Comment by Eric Milkie [ 14/Apr/17 ] |
|
Yes. See |