On 3/30/2018 10:24 PM, Randy Fradin wrote:
I understand from reading the discussion in SOLR-6820 that 65536 is the
recommended default for this setting now because it results in higher
document write rates than the old default of 256. I would like to reduce my
heap utilization and I'm OK with
I have a SolrCloud cluster (version 6.5.1) with around 3300 cores per
instance. I've been investigating what is driving heap utilization since it
is higher than I expected. I took a heap dump and found the largest driver
of heap utilization is the array of VersionBucket objects in the
For a simple illustration of Charlie's point and a side bonus on the 78 reasons
to use the ICUFoldingFilter if you happen to be processing Arabic script
languages, see slides 31-33:
On 3/30/2018 7:18 AM, Terry Steichen wrote:
The output resembles the contents of security.json, except that there's
only one authenticated user, which is the one whose credentials are
supplied. And there are only two permissions.
I was actually wanting to SEE it. Redact things like the
On 03/29/2018 11:07 PM, Shawn Heisey wrote:
> On 3/29/2018 8:28 PM, Terry Steichen wrote:
>> When I set up the initial authentications and authorizations (I'm using
>> 6.6.0 and running in cloud mode.), I call "bin/solr auth enable
>> -credentials xxx:yyy".
>
> What does this command output?
On 3/30/2018 6:01 AM, hal...@xsmail.com wrote:
WHY that works, that's still an open question for me ...
If you had tried the "-x" trick, it might have given me some insight.
But if your solution is acceptable to you, then we can let the matter
drop. If you ever upgrade Solr, you're
hi
On Thu, Mar 29, 2018, at 10:35 AM, Shawn Heisey wrote:
> Looks fine. It's a little odd to be changing the install location to
> /opt/solr instead of /opt ... but if that's what you really want, it
> won't cause any issues.
Just testing that it does what I want, where I want. I always *1st*
