[SERVER-31469] WiredTiger queryable restore engine does not export init function symbol on windows Created: 09/Oct/17 Updated: 30/Oct/23 Resolved: 09/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.4.9 |
| Fix Version/s: | 3.4.11, 3.6.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Steve Briskin (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, on-prem-3.6.0-rc0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Sprint: | Storage 2017-11-13 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Current Ticket Scope: Original ticket description (was configuration error): Command: mongodb-win32-x86_64-enterprise-windows-64-3.4.9\bin\mongod.exe --config .\test_dbs\queryable\59db7af3686b370558ba4519\dbpath/conf.yaml Yaml:
MongoDB Log:
This could be a yaml formatting issue. I tried to rule out the "/" vs. "\" in paths as the cause, but all led to the same fasserts. |
| Comments |
| Comment by Githook User [ 27/Nov/17 ] | |
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: (cherry picked from commit 3bb40ba02b31e6685e84b576b533725b8beb6d20) | |
| Comment by Githook User [ 09/Nov/17 ] | |
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: | |
| Comment by Ian Whalen (Inactive) [ 24/Oct/17 ] | |
|
Fine to repurpose this or make a new one - which works for you. I just want to make sure Steve doesn't lose track of the request here. | |
| Comment by Daniel Gottlieb (Inactive) [ 24/Oct/17 ] | |
|
There might be a (different) server change, but I need Steve to confirm for me. If that's the case, should we plan to open up a new ticket then, or rather re-purpose this one? | |
| Comment by Ian Whalen (Inactive) [ 24/Oct/17 ] | |
|
daniel.gottlieb and steve.briskin since there's no Server code change here, should this just be resolved? I think SERVER tickets might not show up on the Cloud team's In Progress view, even if assigned? CC david.dana | |
| Comment by Daniel Gottlieb (Inactive) [ 21/Oct/17 ] | |
|
I don't have any of the real queryable pieces up and running, but I'm pessimistic the error I'm getting now means will be the next one you hit as well.
Let me know if you hit that as well. In the meantime I'll bring in some windows expertise. | |
| Comment by Daniel Gottlieb (Inactive) [ 21/Oct/17 ] | |
|
The storage.dbPath needs to have its backslashes escaped java-style. Normally the dbpath is passed to WT via its own argument. Not as part of the config string. However, queryable needs to pass it as part of the config string. WT treats backslashes as an escape character. The double backslash is used to write an actual backslash. | |
| Comment by Daniel Gottlieb (Inactive) [ 13/Oct/17 ] | |
|
[daniel.gottlieb believes there will not be a server change required, but rather just communicating to backup what the problem is with the yaml configuration. |