Hi
I am wondering if anyone has attempted Matrix Factorization possible with
Streams in Solr? If so, any pointers would be appreciated.
thanks
Vidhya
On 1/30/2019 3:36 PM, Bharath Kumar wrote:
Thanks Erick. We cleanup the zookeeper state on every installation, so the
zookeeper states are gone. So what should we do in case of a new 7.6
installation where we want to manually create core.properties and use the
non-legacy cloud option? Is it in or
Thanks Erick. We cleanup the zookeeper state on every installation, so the
zookeeper states are gone. So what should we do in case of a new 7.6
installation where we want to manually create core.properties and use the
non-legacy cloud option? Is it in order to use non-legacy cloud, we should
use th
Probably one of the PDFs is corrupted. As you are writing the routine to
upload them try to isolate those who are throwing the exception.
Regards,
Edward
Em qua, 30 de jan de 2019 17:49, Monique Monteiro Hi all,
>
> I'm writing a Python routine to upload thousands of PDF files to Solr, and
> aft
I'm trying to setup CDCR but I'm running into an issue where one or two
shards/replicas will not be replicated but the rest will out of the six
cores.
The only error that appears in the logs is: "Unable to locate core".
Occasionally restarting the instance will fix this but then the issue will
r
Hi all,
I'm writing a Python routine to upload thousands of PDF files to Solr, and
after trying to upload some files, Solr reports the following error in a
HTTP 500 response:
"by: java.util.zip.DataFormatException: invalid distance too far back"
Does anyone have any idea about how to overcome th
"Sometimes for one of the sub-shards, the new leader and one of the new
followers end up on the same instance"
Actually, it seems to be the case that every single time in the entire history
of SPLITSHARD for one of the sub-shards, both the new leader and one of the new
followers end up on the e
I'm not sure what the expected behavior is. However, as of 7.4.0, it
doesn't seem like there is any attempt to prevent both the new leader and
follower replicas from being created on the same instance.
Sometimes for one of the sub-shards, the new leader and one of the new
followers end up on the s
Thank you Eric,
Actually I have figured this out, but there is a deeper problem: where do
these messages come from? They are internal messages. If I suppress messages
from "org.apache.solr.servlet.HttpSolrCall" I will suppress all query
reporting and I do not want this. So the question is what is
Hello,
I have a followup question on SPLITSHARD behavior. I understand that after
a split, the leader replicas of the sub shards would reside on the same
node as the leader of the parent. However, is there an expected behavior
for the follower replicas of the sub shards as to where they will be
cre
On 1/30/2019 2:27 AM, sachin gk wrote:
To support an existing functionality we have turned the opensearcher to
false. Is there a way to flush the cache programiticaly.
Executing a commit with openSearcher=true is the only way I know of
without custom code.
When you commit with openSearcher s
Full class name is "org.apache.solr.servlet.HttpSolrCall"
which you should be able to set to WARN level in log4j2.xml.
DEBUG is definitely _not_ what you want as it dumps
more information
BTW, if you want to see the full path in the log file, you can change
the patternlayout in log4j2.xml to s
This seems very confused. When you say your zookeeper
state is new, you mean there's no remnant of your old 6.1
collection? Then manually creating a core.properties file
won't do you any good as there's no collection to add it to.
You cannot just create a core.properties file and expect Solr
to re
My suggestion is "don't do that" ;).
Ok, seriously. Conceptually what you have is an N-dimnensional matrix.
Each "dimension" is
one of your pivot fields with one cell for each unique value in the
field. So the size is
(cardinality of field 1) x (cardinality of field 2) * (cardinality of
field 3) .
I'd also ask why you care? What benefit do you think you'd get
if you did explicitly flush the document cache?
You seem to think there's some benefit to programmatically
flushing the cache, but you haven't stated what that benefit is.
I suspect that you are making some assumptions that are not tr
Hello:
I'm running Solr Cloud 7.6.0. When I add a node to an existing cluster
that has some collections and replicas, I end up with several suggested
actions under the Suggestions api endpoint. Is there some setting I can
turn on to just make these automatically happen when nodes join or leave?
You don’t need to do that. When there is a commit, Solr creates a new Searcher
with an empty document cache.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 29, 2019, at 10:27 PM, sachin gk wrote:
>
> Hi All,
>
> Is there a way to clear the *do
Hi Shawn,
Thank you for the explanation.
Regards,
Edwin
On Wed, 30 Jan 2019 at 15:18, Shawn Heisey wrote:
> On 1/28/2019 10:14 AM, Zheng Lin Edwin Yeo wrote:
> > We have the following TieredMergePolicyFactory configuration in our
> > solrconfig,xml
> >
> > class="org.apache.solr.index.TieredM
Dear all,
we have a solrcloud cluster with the following features:
- 3 zookeeper nodes
- 4 solr nodes with:
- 4 CPU
- 16GB RAM
Each solr instance is configured as follow:
SOLR_JAVA_MEM="-Xms2g -Xmx8g"
SOL
Thanks Shawn,
To support an existing functionality we have turned the opensearcher to
false. Is there a way to flush the cache programiticaly.
Regards,
Sachin
On Wed, Jan 30, 2019, 12:58 PM Shawn Heisey On 1/29/2019 11:27 PM, sachin gk wrote:
> > Is there a way to clear the *document cache* aft
20 matches
Mail list logo
