Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
1.7.1
-
None
-
None
-
(copied to CRM)
-
Not Needed
Description
I looked into this community forum post and I think it describes a real bug.
Summary
Almost all operations use a composite server selector that includes a LatencySelector to filter out high-latency servers.
See default Collection read selector:
description.CompositeSelector([]description.ServerSelector{
|
description.ReadPrefSelector(rp),
|
description.LatencySelector(db.client.localThreshold),
|
})
|
However, the ChangeStream server selector seems to not use a LatencySelector, only a ReadPrefSelector.
cs := &ChangeStream{
|
client: config.client,
|
registry: config.registry,
|
streamType: config.streamType,
|
options: options.MergeChangeStreamOptions(opts...),
|
selector: description.ReadPrefSelector(config.readPreference),
|
cursorOptions: config.client.createBaseCursorOptions(),
|
}
|
Is that intentional or a bug?
Attachments
Issue Links
- duplicates
-
GODRIVER-2143 Clarify server selection process for change stream resume
-
- Closed
-
- is depended on by
-
GODRIVER-446 Add option for applications to register a custom server selector
-
- Closed
-
- is related to
-
GODRIVER-563 The writeSelector property in the mongo.Database struct should include the LatencySelector
-
- Closed
-