[JAVA-787] DBTCPConnector._checkWriteError () consume a PoolOutputBuffer not returned to SimplePool Created: 15/Mar/13 Updated: 02/May/13 Resolved: 16/Mar/13 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Performance |
| Affects Version/s: | 2.9.3 |
| Fix Version/s: | 2.11.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | barry | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | driver | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ubuntu10, jdk1.6,mongodb2.0.3, mongo-java-driver-2.9.3 |
||
| Issue Links: |
|
||||
| Description |
|
MongoDB Java Driver every time execution update method will from to get a PoolOutputBuffer in SimplePool, returned to the pool after use, but when set WriteConcern for SAFE mode, the drive itself will perform DBTCPConnector._checkWriteError () method to check the safety of the method from the pool made a PoolOutputBuffer, after not returned to the pool, this will consume a PoolOutputBuffer, and this PoolOutputBuffer default at least occupy more than 50KByte memory space, and a tremendous waste of resources.When high concurrent to monitoring jvm memory usage knew terror Eden area is growing very fast. |
| Comments |
| Comment by auto [ 15/Mar/13 ] |
|
Author: {u'date': u'2013-03-15T19:34:31Z', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |
| Comment by Jeffrey Yemin [ 15/Mar/13 ] |
|
Thank you for the bug report. I see the problem and will have a fix for it soon, in the upcoming 2.11.0 release. |