[JAVA-3154] Why does createMachineIdentifier take a long time to run? Created: 29/Jan/19 Updated: 11/Sep/19 Resolved: 29/Jan/19 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | BSON |
| Affects Version/s: | 4.0.0 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Zeemann | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Using Bitmani supplied docker image, bitnami/mongodb:4.1 |
||
| Description |
|
We are running unit tests as part of maven initiated testing which indirectly creates mongo connections, these seem to take some time to startup and we are seeing lots of time calling createMachineIdentifier; e.g. Is there any way to shorten the amount of time being spend calling createMachineIdentifier? |
| Comments |
| Comment by Matthew Zeemann [ 30/Jan/19 ] |
|
Again, thanks ... |
| Comment by Jeffrey Yemin [ 30/Jan/19 ] |
|
We haven't set a release date, but it should be soon. All the issues currently slated for the release have been fixed, and we're evaluating whether to bring anything else in. |
| Comment by Matthew Zeemann [ 30/Jan/19 ] |
|
Any idea on when 3.10 will be publicly available? The latest mvnrepository.com has is 3.91 |
| Comment by Jeffrey Yemin [ 29/Jan/19 ] |
|
The 3.10 will be binary-compatible with the 3.8 release so you will be able to override the dependency in your own project's configuration, and everything should work fine. |
| Comment by Matthew Zeemann [ 29/Jan/19 ] |
|
Thanks, Jeff Have checked spring-data-mongodb/pom.xml and its only using 3.8.2 |
| Comment by Jeffrey Yemin [ 29/Jan/19 ] |
|
Hi matthewzeemann, It's only called once, in a static initializer, so in practice this should not be a problem. However, in the upcoming 3.10 release the whole method is gone, so you should no longer see it show up in profiles once you upgrade. |