[SERVER-31719] Long overflow in setParameter Created: 25/Oct/17  Updated: 06/Feb/18  Resolved: 06/Feb/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.2.12, 3.4.10
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Crimson Glory Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Duplicate Votes: 0
Labels: platforms-needs-37-triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-30389 Simple and generic way to restrict se... Closed
Operating System: ALL
Steps To Reproduce:

1. Login to mongo shell
2. Input command with a huge number
3. Check the new value

Participants:

 Description   

I wanted to disable the cursorTimeout, since I do huge aggregate queries (and no_cursor_timeout does not exist for aggregate framework).

I accidentaly found a long integer overflow:

> db.getSiblingDB('admin').runCommand( { setParameter: 1, cursorTimeoutMillis: 2592000000 } )
{ "was" : 18000001, "ok" : 1 }
> db.getSiblingDB('admin').runCommand( { setParameter: 1, cursorTimeoutMillis: 2592000001 } )
{ "was" : -2147483648, "ok" : 1 }



 Comments   
Comment by Andrew Morrow (Inactive) [ 06/Feb/18 ]

Hi - I'm closing out this ticket in favor of SERVER-30389, which describes the underlying problem that leads to this symptom. Fixing SERVER-30389 would address the issue here. Please watch SERVER-30389 for updates, or reach out to us there if we can provide more information.

Comment by Mark Agarunov [ 26/Oct/17 ]

Hello CrimsonGlory,

Thank you for the report. Using the provided command, I've managed to reproduce the issue. I've set the fixVersion on this ticket to 'Needs Triage' for this to be scheduled against out currently planned work. Updates will be posted on this ticket as they are available.

Thanks,
Mark

Generated at Thu Feb 08 04:27:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.