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
