Skip to content

Conversation

corentinbaron
Copy link
Contributor

Having mongoDB using the system page size requires quite some work, yet it works fine on PPC 64 with a 64kB page size (which is the case on Ubuntu 14.04 Little Endian).

@benety
Copy link
Contributor

benety commented Aug 8, 2014

Hi Corentin,

Thanks for signing the contributor's agreement. I can't seem to find a SERVER ticket in our JIRA queue for this pull request. Could you please create one here?

https://jira.mongodb.org/browse/SERVER

Regards,
Ben

@corentinbaron
Copy link
Contributor Author

here it is: https://jira.mongodb.org/browse/SERVER-14835

Also, we'd like to have this also on 2.6, should I submit a pull request on the 2.6.4-rc0 branch?

@benety benety changed the title Disabling the assert 16143 on PowerPC 64 SERVER-14835 Disabling the assert 16143 on PowerPC 64 Aug 8, 2014
@benety
Copy link
Contributor

benety commented Aug 8, 2014

Hi Corentin,

Pull requests are handled by setting the Backport field in the SERVER ticket to Requested. If the SERVER ticket is resolved and the Backport is approved, we will cherry-pick the commit to the upcoming 2.6 branch.

Regards,
Ben

@benety benety changed the title SERVER-14835 Disabling the assert 16143 on PowerPC 64 SERVER-14835 fix fassert 16143 on PPC64 LE systems in LogFile::synchronousAppend() Aug 14, 2014
@benety
Copy link
Contributor

benety commented Aug 20, 2014

Hi @corentinbaron,

Have you read @andy10gen and @kangas's comments on the SERVER-14835 ticket?

I don't think we can merge this pull request in its current form because the right thing to do would be to fix the expression in the fassert() itself, not disable it.

Please let us know if you are interested in updating your patch based on the recommendations in the SERVER ticket.

Regards,
Ben

@benety
Copy link
Contributor

benety commented Aug 25, 2014

Hi @corentinbaron,

We have not heard from you in a while.

Since we cannot move forward on this pull request in its current form, we will be closing it.

If you decide to implement the recommendations proposed in SERVER-14835, please do not hesitate to re-open this pull request and we'll be happy to review it.

Regards,
Ben

@benety
Copy link
Contributor

benety commented Sep 26, 2014

Replaced by #769

@Gayatri31
Copy link

hello, i know that this is not related to this post but help me......
i have a requirement where i have make the document names dynamic means for eg: my document name is company_address in company collection and iam assigning this document name to a variable and using it in where condition but its not working...
...
var address="company_address";
db.company.find({address:"USA"})
...
Can any one help me to fix this problem.....

@kangas
Copy link
Contributor

kangas commented Sep 30, 2014

@Gayatri31, the best place to get answers about how to use MongoDB is the mongodb-user Google Group

Your question is a matter of Javascript syntax. Try this instead:

// Build query document. Cannot use object literal syntax for variable keys.
var toFind = {};
toFind["company_address"] = "USA";

// Use query document
db.company.find(toFind);

jiongle1 pushed a commit to scantist-ossops-m2/mongo that referenced this pull request Mar 30, 2024
Minor bug fixes in eviction.
jiongle1 pushed a commit to scantist-ossops-m2/mongo that referenced this pull request Mar 30, 2024
… this assertion:

btree/bt_discard.c, 45: !F_ISSET_ATOMIC(page, WT_PAGE_EVICT_LRU)

refs mongodb#735
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants