[WT-2081] WiredTiger verify progress reporting too verbose Created: 03/Sep/15  Updated: 12/Oct/17  Resolved: 03/Sep/15

Status: Closed
Project: WiredTiger
Component/s: None
Affects Version/s: None
Fix Version/s: WT2.7.0

Type: Bug Priority: Major - P3
Reporter: Alexander Gorrod Assignee: Alexander Gorrod
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Depends
is depended on by SERVER-20060 WiredTiger changes for MongoDB 3.1.8 Closed
Related
related to SERVER-20179 wiredtiger progress reporting is too ... Closed

 Description   

The WiredTiger verify command currently reports progress for each table and each 10 pages in a file. Verifying lots of small tables in a database can lead to a lot of verify progress messages.

Progress messages are designed for applications to monitor long running operations - it makes sense for the reporting to be less verbose.



 Comments   
Comment by Githook User [ 03/Sep/15 ]

Author:

{u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexg@wiredtiger.com'}

Message: WT-2081 Make verify progress reporting less verbose.
Branch: develop
https://github.com/wiredtiger/wiredtiger/commit/b4aa30d25b1788a082a2dfe79e215ceb2261ec9c

Comment by Githook User [ 03/Sep/15 ]

Author:

{u'username': u'keithbostic', u'name': u'Keith Bostic', u'email': u'keith@wiredtiger.com'}

Message: WT-2081: don't bother with a wrap-up verbose progress message, it
doesn't add any value.

Replicate the changes to keep verify from being so verbose into
salvage, it potentially has the same problem.
Branch: develop
https://github.com/wiredtiger/wiredtiger/commit/0a154cfd16d26df4047d8252bdcc97e273f93fc1

Comment by Githook User [ 03/Sep/15 ]

Author:

{u'username': u'keithbostic', u'name': u'Keith Bostic', u'email': u'keith.bostic@mongodb.com'}

Message: Merge pull request #2170 from wiredtiger/verify-less-progress-reports

WT-2081 Make verify progress reporting less verbose.
Branch: develop
https://github.com/wiredtiger/wiredtiger/commit/9734d8523b7ad858b1c52de0a08808b3d9e8544f

Generated at Wed Sep 26 08:46:07 UTC 2018 using Jira 7.12.1#712002-sha1:609a50578ba6bc73dbf8b05dddd7c04a04b6807c.