In the solr.in.sh script I do see this:
# Set the thread stack size
SOLR_OPTS="$SOLR_OPTS -Xss256k"

I don't remember ever changing this, but it's only there once

I can't find a reference to +UseGCLogFileRotation at all.

I don't see anyplace where we set either of these twice.

We were migrating from solr 6.2.0 if that makes any difference

On Wed, Nov 15, 2017 at 12:55 PM, Shawn Heisey <apa...@elyograg.org> wrote:

> On 11/15/2017 8:40 AM, Webster Homer wrote:
> > I do see errors in both Consoles. I see more errors on the ones that
> don't
> > display Args
> > Here are the errors that only show up when Args doesn't:
> > Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed. Use
> > 'track by' expression to specify unique keys. Repeater: arg in
> > commandLineArgs, Duplicate key: string:-XX:+UseGCLogFileRotation,
> Duplicate
> > value: -XX:+UseGCLogFileRotation
> <snip>
> > angular.js:11617 Error: [ngRepeat:dupes] Duplicates in a repeater are not
> > allowed. Use 'track by' expression to specify unique keys. Repeater: arg
> in
> > commandLineArgs, Duplicate key: string:-Xss256k, Duplicate value:
> -Xss256k
> >
>
> This was the clue I needed.
>
> I added this line to the end of solr.in.cmd (I'm doing this testing on
> Windows):
>
> set SOLR_OPTS=%SOLR_OPTS% -Xss256k
>
> With that change and a Solr restart, the Args information disappeared
> from the admin UI.
>
> Somewhere, likely in your include script, you have defined custom
> arguments that have duplicated the -Xss256k and
> -XX:+UseGCLogFileRotation arguments that are included by default.  There
> may be other duplicates, but those are the ones that were included in
> the error information you shared.  If you adjust the startup
> configuration so that there are no duplicate commandline arguments, then
> restart Solr, it should display.
>
> This does mean that Solr has a bug in the admin UI, but it's one that
> you can work around by removing duplicate arguments.  The angular code
> used for the argument display cannot handle duplicate entries.  Here's
> the issue I created for the problem:
>
> https://issues.apache.org/jira/browse/SOLR-11645
>
> There's a patch attached to the issue that fixes the problem for me, and
> some instructions for fixing up a binary download with that change
> rather than a source checkout.
>
> Thanks,
> Shawn
>
>

-- 


This message and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. If you are not the intended recipient, 
you must not copy this message or attachment or disclose the contents to 
any other person. If you have received this transmission in error, please 
notify the sender immediately and delete the message and any attachment 
from your system. Merck KGaA, Darmstadt, Germany and any of its 
subsidiaries do not accept liability for any omissions or errors in this 
message which may arise as a result of E-Mail-transmission or for damages 
resulting from any unauthorized changes of the content of this message and 
any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its 
subsidiaries do not guarantee that this message is free of viruses and does 
not accept liability for any damages caused by any virus transmitted 
therewith.

Click http://www.emdgroup.com/disclaimer to access the German, French, 
Spanish and Portuguese versions of this disclaimer.

Reply via email to