[CSHARP-646] Fix various serialization bugs in SystemProfileInfoSerializer Created: 12/Dec/12  Updated: 20/Mar/14  Resolved: 28/Dec/12

Status: Closed
Project: C# Driver
Component/s: None
Affects Version/s: 1.7
Fix Version/s: 1.8

Type: Bug Priority: Major - P3
Reporter: Robert Stam Assignee: Robert Stam
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to CSHARP-647 Improvements to TimeSpanUnits and Tim... Closed
Backwards Compatibility: Fully Compatible

 Description   

This description is from pull request: https://github.com/mongodb/mongo-csharp-driver/pull/144

Problems:

The SystemProfileInfoSerializer used the name "lockStatMillis" for the lock statistics key name. At least in MongoDB 2.2 the correct name is "lockStats"

The SystemProfileLockStatisticsSerializer used the names "timeAcquiring" and "timeLocked" where the right names are "timeAcquiringMicros" and "timeLockedMicros".

The timespan units used were milliseconds, where the correct units are microseconds. Added the option MicroSeconds to the TimeSpanSerializer and set the SystemProfileReadWriteLockStatisticsSerializer to use Microseconds.

NOT FIXED: The TimeSpanUnits.Nanoseconds is wrong. 1 millisecond is not 1000 nanoseconds, its 1000000 nanoseconds. This option should probably be removed since TimeSpan doesn't have nanosecond precision (most accurate precision is ticks, where 10000 ticks are one millisecond).



 Comments   
Comment by auto [ 27/Dec/12 ]

Author:

{u'date': u'2012-12-26T20:54:39Z', u'email': u'robert@10gen.com', u'name': u'rstam'}

Message: CSHARP-646: added new properties to SystemProfileInfo for server 2.2.
Branch: master
https://github.com/mongodb/mongo-csharp-driver/commit/351e4ba8425fc7306d4ba4d158f0060019bc8d47

Generated at Wed Feb 07 21:37:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.