Ok. Still hard to follow. Can you clarify which collection you run these
queries on?
Collection name (url segment before /select) is more significant than any
port (jvm) identity.
On Wed, Aug 21, 2019 at 5:14 AM Lisheng Wang
wrote:
> Hi Mikhail
>
> Thanks for your response, but question is not
Hi Mikhail,
okay.
below is 2 requests:
both are select from "movieDirectors" collection join "movies" collection
which has 2 shards.
http://localhost:8983/solr/movieDirectors/select?fq=%7B!join%20from%3Ddirector_id%20fromIndex%3Dmovies%20to%3Did%7Dtitle%3A%22Dunkirk%22&q=*%3A*
http://localhost
Hi Jason,
Thanks for your prompt reply.
Your code does address few of my concerns like restricting *solr-user* from
accessing the dashboard and from executing other request methods apart from
*"update"* and *"read"*.
But I am still able to access other collections such as *"Collection3",
"Collec
Hello,
Looking this up i found SOLR-5692, but that was solved a lifetime ago, so just
checking if this is a familiar error and one i missing in Jira:
A client's Solr 8.2.0 cluster brought us the next StackOverflowError while
running 8.2.0 on Java 8:
Exception in thread "coreZkRegister-1-thread
Hi Arnold,
It’s hard to say without seeing exactly what you’re doing and exactly what
you’re seeing.
Simplify it first, ie remove your custom plugins and related config and see if
the problem reproduces still, then try without cloud mode and see it it
reproduces still. Then create an issue on
The "all" permissions _should_ block solr-user from accessing all of
those resources, and I believe it does in newer versions of Solr.
There was a bug with it that was fixed a few versions back though- it
sounds like you might be running into that. (see
https://issues.apache.org/jira/browse/SOLR-13
Hi Jason,
I am using version 7.6 of Solr.
Thanks,
Salmaan
On Wed, Aug 21, 2019 at 4:12 PM Jason Gerlowski
wrote:
> The "all" permissions _should_ block solr-user from accessing all of
> those resources, and I believe it does in newer versions of Solr.
> There was a bug with it that was fixed
Hi Jason,
Is there a way to fix this in version 7.6?
Or is it mandatory to upgrade to other versions?
If I have to upgrade to a higher version, then what is the best way to do
this without effecting the current configuration and indexed data?
Thanks,
Salmaan
On Wed, Aug 21, 2019 at 4:13 PM S
Ah, ok. SOLR-13355 still affects 7.6, so that explains why you're
seeing this behavior.
You could upgrade to get the new behavior, but you don't need to-
there's a workaround. You just need to add a few extra rules to your
security.json. The problem in SOLR-13355 is that the "all" permission
is
I'm not sure, but it might be an issue. It make sense to add negative test
and assert the exception at
https://github.com/apache/lucene-solr/blob/master/solr/core/src/test/org/apache/solr/cloud/DistribJoinFromCollectionTest.java
On Wed, Aug 21, 2019 at 10:37 AM Lisheng Wang
wrote:
> Hi Mikhail,
> Looking this up i found SOLR-5692, but that was solved a lifetime ago,
It wasn't.
https://issues.apache.org/jira/browse/SOLR-5692?focusedCommentId=14556876&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14556876
On Wed, Aug 21, 2019 at 1:29 PM Markus Jelsma
wr
Hi,
I am facing issue on my solr master, getting this in logs:
2019-08-19 22:29:55.573 ERROR (qtp59559151-101) [ ] o.a.s.s.HttpSolrCall
null:org.apache.solr.common.SolrException: SolrCore 'sitecore_contents_index'
is not available due to init failure: Error opening new searcher
Hi Jason,
Unfortunately, the above mentioned workaround does not work for me.
I modified your script a little bit as follow and it still doesn't work.
{"name": "update", "collection": ["collection1", "collection2"],
"role": "dev"},
{"name": "read", "collection": ["collection1", "collection2"],
I think it would be useful to provide additional details like solr version,
when did you start seeing the problem? Did you upgrade lately?
Did you change anything?
On Wed, Aug 21, 2019 at 2:17 PM Akreeti Agarwal wrote:
> Hi,
>
> I am facing issue on my solr master, getting this in logs:
>
> 2019
I happened to see this, Ritesh, so let me offer that this issue (#178247) is
addressed in the Sitecore 9 version:
https://dev.sitecore.net/Downloads/Sitecore%20Experience%20Platform/90/Sitecore%20Experience%20Platform%2090%20Update2/Release%20Notes.
That fix, however, resolves the issue ONLY for
I bet this is the problem:
java.nio.file.NoSuchFileException: /solr-m/server/solr/sitecore_c
Do you have any idea about why Solr us not finding that datafile?
Andrea
On Wed, 21 Aug 2019, 14:41 Atita Arora, wrote:
> I think it would be useful to provide additional details like solr version,
>
You’d also probably get more information from the Sitecore folks, Apache Solr
is used by Sitecore, but doesn’t know much about Sitecore issues.
Offhand I’d check if your disk is at or near full. Going just from the
“rebuild” mention, looks like the index is being recreated, in which case there
SOLR version is : solr-5.5.5
Thanks & Regards,
Akreeti Agarwal
-Original Message-
From: Akreeti Agarwal
Sent: Wednesday, August 21, 2019 5:47 PM
To: solr-user@lucene.apache.org
Subject: Solr master issue
Hi,
I am facing issue on my solr master, getting this in logs:
2019-08-19 22:29
Hi Grant,
Thank you for the response!
The Sitecore version is 9.0 update 2 and we already have applied the patch you
mentioned below (which I was referring earlier) but still the issue (random
times) would be observed sometimes.
Note: We have to restart the solr-zk ensemble + Sitecore VM to h
Hi Jorn,
I was finally able to get the entire cluster back up on http. I ended up
having to reload the collection from the Web interface on each individual
server and then restart the members 1 at a time until 1 of them came up as
master and was able to locate and load the core.
I am still not sur
Hi, does anybody know why Solr Java process is terminated with no reason?
The OOM script does not run. In the server logs does not show anything.
Solr is running with 25g of Java heap and only using 20%.
--
*Adriano Melo*
Tel.: (83) 98875-1868
Hi Adriano,
Can you provide more information around what are you doing? Answers to
questions like the following would be very useful for anyone who might try
to help you here:
1. What version of Solr are you using?
2. Is this vanilla, or are you using something custom w.r.t. the code as
well as c
On 8/21/2019 4:44 PM, Adriano Rogério de O. Carolino de Melo wrote:
Hi, does anybody know why Solr Java process is terminated with no reason?
What OS is it running on? Maybe it's the OS killing it. How did you
install/start Solr, and what version is it?
The OOM script does not run. In the
Hi Everybody,
we are using Apache Solr strongly with nested documents feature. But in
version 8 we noticed that the highlighting which has been worked in Version 7
doesn't work properly in Version 8 . It works only for root parent element but
not for childs? Is this an known open issue or shou
Few deatils added.
public void close() {
int count = refCount.decrementAndGet();
if (count > 0) return; // close is called often, and only actually
closes if nothing is using it.
if (count < 0) {
log.error("Too many close [count:{}] on {}. Please report this
exception to solr-us
Few deatils added.
public void close() {
int count = refCount.decrementAndGet();
if (count > 0) return; // close is called often, and only actually
closes if nothing is using it.
if (count < 0) {
log.error("Too many close [count:{}] on {}. Please report this
exception to solr-us
Hi,
Any suggestions as to what can be done?
Regards,
Salmaan
On Wed, Aug 21, 2019 at 4:33 PM Jason Gerlowski
wrote:
> Ah, ok. SOLR-13355 still affects 7.6, so that explains why you're
> seeing this behavior.
>
> You could upgrade to get the new behavior, but you don't need to-
> there's a wo
27 matches
Mail list logo
