[
https://issues.apache.org/jira/browse/SOLR-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280033#comment-17280033
]
Mike Drob commented on SOLR-15133:
----------------------------------
The origin seems to be from [~elyograg]'s wiki page, where he comments that:
{quote}A note about the UseLargePages option: Currently I do not have huge
pages allocated in my operating system. This option will not actually do
anything unless you allocate memory to huge pages. If you do so, memory usage
reporting with the “top” command will probably only show a few hundred MB of
resident memory used by your Solr process, even if it is in fact using several
gigabytes of heap. If you do enable huge pages in Linux, be aware that you
might wish to turn off an operating system feature called transparent huge
pages.{quote}
I don't understand enough of this quote to assert under what conditions large
pages are useful. Perhaps we can attempt to auto-detect the conditions based on
1) Specified Java Heap Size 2) Underlying system support and selectively enable
the flag then?
> Document how to eliminate Failed to reserve shared memory warning
> -----------------------------------------------------------------
>
> Key: SOLR-15133
> URL: https://issues.apache.org/jira/browse/SOLR-15133
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Docker, documentation
> Affects Versions: 8.7
> Reporter: David Eric Pugh
> Assignee: David Eric Pugh
> Priority: Minor
> Fix For: master (9.0)
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> inspired by a conversation on
> [https://github.com/docker-solr/docker-solr/issues/273,] it would be good to
> document how to get rid of shared memory warning in Docker setups.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
