[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.

2017-04-14T10:18:10.924+0000 I STORAGE  [conn327] WiredTiger progress WT_SESSION.verify 21400
2017-04-14T10:18:10.936+0000 I STORAGE  [conn327] WiredTiger progress WT_SESSION.verify 21500
2017-04-14T10:18:23.938+0000 W STORAGE  [conn327] verify() returned EBUSY. Not treating as invalid.

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 SERVER-23131.

Generated at Thu Feb 08 04:19:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.