-
Type:
Improvement
-
Status: Accepted
-
Priority:
Minor - P4
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
It would be useful to provide context around any errors and messages, like these connection ones to include:
- What operation was executed when it occurred
- What action will be taken due to the information
- Does this message indicate a problem or something that can be "fixed" in any way.
2016-01-28T21:31:15.149+0000 error: read tcp 10.32.12.66:27017: connection timed out
|
2016-01-28T21:31:15.655+0000 [#######.................] db.coll 73.6 GB/229.9 GB (32.0%)
|
2016-01-28T21:31:15.867+0000 error: read tcp 10.32.12.66:27017: connection timed out
|
2016-01-28T21:31:16.009+0000 error: read tcp 10.32.12.66:27017: connection timed out
|
2016-01-28T21:31:16.462+0000 error: read tcp 10.32.12.66:27017: connection timed out
|
2016-01-28T21:31:17.108+0000 error: read tcp 10.32.12.66:27017: connection timed out
|
2016-01-28T21:31:18.171+0000 error: read tcp 10.32.12.66:27017: connection timed out
|
2016-01-28T21:31:18.488+0000 error: read tcp 10.32.12.66:27017: connection timed out
|
2016-01-28T21:31:18.659+0000 [#######.................] db.coll 73.8 GB/229.9 GB (32.1%)
|
2016-01-28T21:31:18.890+0000 error: read tcp 10.32.12.66:27017: connection timed out
|
Suggested example with more context:
2016-01-28T21:31:18.890+0000 error during batch insert (coll-name): read tcp 10.32.12.66:27017: connection timed out -- retrying batch insert
|
// or
|
2016-01-28T21:31:18.890+0000 error during batch insert (coll-name): read tcp 10.32.12.66:27017: connection timed out -- not retrying batch insert
|
// or
|
2016-01-28T21:31:18.890+0000 error during batch insert (coll-name): read tcp 10.32.12.66:27017: connection timed out -- ignoring error
|
This happened in mongorestore but I imagine it could happen in any of the tools.
- is duplicated by
-
-
- Closed
-