Extending SOLR default/eDisMax query parser with Span queries functionalities
Hi, We would like to extend SOLR default (named 'lucene' per: https://lucene.apache.org/solr/guide/6_6/the-standard-query-parser.html) or eDisMax query parser with additional functionality of Lucene Span queries in order to allow via standard parsers to execute position search (SpanFirst, etc.) via more trivial interface (for example 'sq=' clause). Is there any guideline/HowTo regarding required areas to focus on/implement, important notes/checklist, etc. ? (the idea I guess is to inherit the default/eDisMax relevant classes and expand functionality, without harming the existing ones) We've found the below try to do something similar, but it was at 2012 and on very old Solr version (4.X), and i assume default SOLR/eDisMax parsers were changed since then (we are on Solr 8.3 version right now). https://issues.apache.org/jira/browse/SOLR-3925 Thanks a lot in advance, Adi This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries. The information is intended to be for the use of the individual(s) or entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail.
source cluster sends incorrect recovery request to target cluster when CDCR is enabled
Hi,
Running Solr 7.7.2, cluster with 3 replicas
When CDCR is enabled, one of the target nodes gets an incorrect recovery
request.
Below is the content of the state.json file from the zookeeper.
"shards":{"shard1":{
"range":"8000-7fff",
"state":"active",
"replicas":{
"core_node3":{
"core":"tbh_manuals_test_bi2_shard1_replica_n1",
"base_url":"https://host1:8983/solr;,
"node_name":"host1:8983_solr",
"state":"active",
"type":"NRT",
"force_set_state":"false"},
"core_node5":{
"core":"tbh_manuals_test_bi2_shard1_replica_n2",
"base_url":"https://host2:8983/solr;,
"node_name":"host2:8983_solr",
"state":"active",
"type":"NRT",
"force_set_state":"false",
"leader":"true"},
"core_node6":{
"core":"tbh_manuals_test_bi2_shard1_replica_n4",
"base_url":"https://host3:8983/solr;,
"node_name":"host3:8983_solr",
"state":"active",
"type":"NRT",
"force_set_state":"false"}}
As we see, host1 doesn't have tbh_manuals_test_bi2_shard1_replica_n4.
However, host1 is receiving the request that
tbh_manuals_test_bi2_shard1_replica_n4 will be recovered, which cause
"unable to locate core" error.
Below is the entire error message of host1 on target cluster
2020-01-08 03:05:52.355 INFO (zkCallback-7-thread-14) [ ]
o.a.s.c.c.ZkStateReader A cluster state change: [WatchedEvent
state:SyncConnected type:NodeDataChanged
path:/collections/tbh_manuals_test_bi2/state.json] for collection
[tbh_manuals_test_bi2] has occurred - updating... (live nodes size: [3])
2020-01-08 03:05:52.355 INFO (zkCallback-7-thread-15) [ ]
o.a.s.c.c.ZkStateReader A cluster state change: [WatchedEvent
state:SyncConnected type:NodeDataChanged
path:/collections/tbh_manuals_test_bi2/state.json] for collection
[tbh_manuals_test_bi2] has occurred - updating... (live nodes size: [3])
2020-01-08 03:05:52.378 INFO (qtp1155769010-87) [
x:tbh_manuals_test_bi2_shard1_replica_n4] o.a.s.h.a.CoreAdminOperation It
has been requested that we recover:
core=tbh_manuals_test_bi2_shard1_replica_n4
2020-01-08 03:05:52.379 ERROR (qtp1155769010-87) [
x:tbh_manuals_test_bi2_shard1_replica_n4] o.a.s.h.RequestHandlerBase
org.apache.solr.common.SolrException: Unable to locate core
tbh_manuals_test_bi2_shard1_replica_n4
at
org.apache.solr.handler.admin.CoreAdminOperation.lambda$static$5(CoreAdminOperation.java:167)
at
org.apache.solr.handler.admin.CoreAdminOperation.execute(CoreAdminOperation.java:360)
at
org.apache.solr.handler.admin.CoreAdminHandler$CallInfo.call(CoreAdminHandler.java:396)
at
org.apache.solr.handler.admin.CoreAdminHandler.handleRequestBody(CoreAdminHandler.java:180)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:199)
at
org.apache.solr.servlet.HttpSolrCall.handleAdmin(HttpSolrCall.java:736)
at
org.apache.solr.servlet.HttpSolrCall.handleAdminRequest(HttpSolrCall.java:717)
at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:496)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:395)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:341)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1602)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:540)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1588)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1557)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
at
Log issue adding a java agent to SOLR_OPTS
Hello, I am trying to add a javaagent to monitor solr using a jmxtans agent. I am using Solr version 7.7 and Java 8. Basically I have added the following line at the end of my solr.in.sh: SOLR_OPTS="$SOLR_OPTS -javaagent:/path/jmxtrans-agent.jar=/path/jmxtrans-agent-config.xml" After add that line Solr startup correctly, I can see with a ps command that "-javaagent:/path/jmxtrans-agent.jar=/path/jmxtrans-agent-config.xml" is added to the java process, and it send jmx metrics to my time series database (InfluxDB), but it stop to write in solr.log log file and it start to writes all the ouput in solr--console.log. Any idea about this behaviour? Thanks in advance.
Log issue adding a java agent to SOLR_OPTS
Hello, I am trying to add a javaagent to monitor solr using jmxtans agent. I am using Solr version 7.7. Basically I have added the following line at the end of my solr.in.sh SOLR_OPTS="$SOLR_OPTS -javaagent:/path/jmxtrans-agent.jar=/path/jmxtrans-agent-config.xml" Solr startup correctly and it send jmx metics to my time series database (InfluxDB) but it stop to write in solr.log file and it start to writes all the ouput in the solr--console.log. I can see with a ps command that "-javaagent:/path/jmxtrans-agent.jar=/path/jmxtrans-agent-config.xml" is added to the java process. Any idea about this behaviour? Thanks in advance.g
Re: Solr 8.4.0 Cloud Graph is not shown due to CSP
here you go: https://issues.apache.org/jira/browse/SOLR-14176 a detailed screenshot of the message can be made tomorrow, but it looks pretty much to CSP to me - i have seen others with other applications using CSP. On Tue, Jan 7, 2020 at 6:45 PM Kevin Risden wrote: > So this is caused by SOLR-13982 [1] and specifically SOLR-13987 [2]. Can > you open a new Jira specifically for this? It would be great if you could > capture from Chrome Dev Tools (or Firefox) the error message around what > specifically CSP is complaining about. > > The other thing to ensure is that you force refresh the UI to make sure > nothing is cached. Idk if that is in play here but doesn't hurt. > > [1] https://issues.apache.org/jira/browse/SOLR-13982 > [2] https://issues.apache.org/jira/browse/SOLR-13987 > > Kevin Risden > > On Tue, Jan 7, 2020, 11:15 Jörn Franke wrote: > > > Dear all, > > > > I noted that in Solr Cloud 8.4.0 the graph is not shown due to > > Content-Security-Policy. Apparently it violates unsafe-eval. > > It is a minor UI thing, but should I create an issue to that one? Maybe > it > > is rather easy to avoid in the source code of the admin page? > > > > Thank you. > > > > Best regards > > > > > > >
solr unable to locate core on CDCR
Whenever I create a new collection on solr 7.7.2 cluster CDCR(uni directional), and once I disable buffer on both source and target nodes and start CDCR process on the source node, then I encounter the error message "solr unable to locate core..." on one of target node. On source node, CDCR bootstrap failed because of the target node's failure to locate core. The exact moment thatthe error message occurs is when I trigger CDCR process on the source node. Is there any bug on solr 7.7.2 CDCR? Following is the steps to reproduce. 1) create collection on both source and target nodes 2) disable buffer on the source and target 3) enable CDCR on source nodes then target node can't locate the core, and the source node failed to start CDCR bootstrap. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Solr 8.4.0 Cloud Graph is not shown due to CSP
So this is caused by SOLR-13982 [1] and specifically SOLR-13987 [2]. Can you open a new Jira specifically for this? It would be great if you could capture from Chrome Dev Tools (or Firefox) the error message around what specifically CSP is complaining about. The other thing to ensure is that you force refresh the UI to make sure nothing is cached. Idk if that is in play here but doesn't hurt. [1] https://issues.apache.org/jira/browse/SOLR-13982 [2] https://issues.apache.org/jira/browse/SOLR-13987 Kevin Risden On Tue, Jan 7, 2020, 11:15 Jörn Franke wrote: > Dear all, > > I noted that in Solr Cloud 8.4.0 the graph is not shown due to > Content-Security-Policy. Apparently it violates unsafe-eval. > It is a minor UI thing, but should I create an issue to that one? Maybe it > is rather easy to avoid in the source code of the admin page? > > Thank you. > > Best regards > > >
Solr 8.4.0 Cloud Graph is not shown due to CSP
Dear all, I noted that in Solr Cloud 8.4.0 the graph is not shown due to Content-Security-Policy. Apparently it violates unsafe-eval. It is a minor UI thing, but should I create an issue to that one? Maybe it is rather easy to avoid in the source code of the admin page? Thank you. Best regards
