Hi,
I'm new to Solr and am trying to set up a newly installed Solr instance.
When I try to create a core via the web interface I get:
Error CREATEing SolrCore 'new_core': Unable to create core [new_core] Caused by:
QueryElevationComponent missing config file: 'elevate.xml either:
I believe this comes when Zookeeper quorum is not maintained. Do not see
any way around except bringing the quorum back?
Thanks,
Susheel
On Thu, Dec 29, 2016 at 9:27 AM, Yago Riveiro
wrote:
> There is any way to recover from a exception
>
There is any way to recover from a exception
"org.apache.solr.common.SolrException: Cannot talk to ZooKeeper - Updates
are disabled" without restart the affected node node?
Regards,
/Yago
-
Best regards
/Yago
--
View this message in context:
Hi,
when i was trying out the SQL functionality, i realized that
multiple order by clauses work only when " select distinct " command is
used where as it does not work with a " select "command
Eg:
SELECT distinct name, salary, distance_from_office FROM "employees_core"
ORDER BY salary desc ,
I'm modifying out custom update handler and the modifications needs access
to a third party jar (microsoft azure).
For what it's worth, I use mvn as my build / packaging tool.
During runtime, I've been encountering class not found errors in the plugin
related to the azure library.
1. Is there
If I lost quorum on Zookeeper, this is a “fault” in the Zookeeper cluster,
therefore I should see something in the logs right?
The question here is, why I need to restart the node again?, if Zookeeper
recover its quorum, the Solr node should be in read-write mode again …
Any ideas how can test
Your assumption is not correct. The Web UI core admin expects that
you've already created the new core's directory and the associated
conf directory below it. Since each core may have a much different
config, there's no good way to pick the right set of configurations,
your schema.xml file which
Hi Vinay,
You need to include libs using lib directives in Solr config:
https://cwiki.apache.org/confluence/display/solr/Lib+Directives+in+SolrConfig.
Regrads,
Emir
On 29.12.2016 19:11, Vinay B, wrote:
I'm modifying out custom update handler and the modifications needs access
to a third
The logs filled up the file system and caused CDCR to fail due to a
corrupted Tlog file.
On Thu, Dec 22, 2016 at 9:10 AM, Webster Homer
wrote:
> While testing CDCR I found that it is writing tons of log messages per
> second. Example:
> 2016-12-21 23:24:41.652 INFO
This would be a bug. I'll take a look at the test cases and see if there is
a test case for this.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Dec 29, 2016 at 3:17 PM, radha krishnan
wrote:
> Hi,
>
> when i was trying out the SQL functionality, i realized
There are test cases with multiple order by fields for SELECT DISTINCT and
GROUP BY. But not for simple SELECT.
We are just about to release a new version of the SQL interface which uses
Apache Calcite rather then Presto. I'll make sure that this is working in
the new release.
Joel Bernstein
Thanks,
I think I already tried that approach
ie. my solr config included the lib directive
and i placed the azure jar in the same "lib" directory as the custom
updatehandler (../contrib/updatehandler/lib) so I expect the rather liberal
wildcard regex would pick it up.
On Thu, Dec 29,
Seems like a bandaid would be to insure your Solr logs rotate
appropriately quickly.
That doesn't address the CDCR loging verbosity, but it might get you by.
You can also change the logging at the class level by appropriately editing the
log4j properties file. Again perhaps not the best solution
Thanks Joel for your reply.
will test it out it in the next version.
Thanks,
Radhakrishnan D
On Thu, Dec 29, 2016 at 12:41 PM, Joel Bernstein wrote:
> There are test cases with multiple order by fields for SELECT DISTINCT and
> GROUP BY. But not for simple SELECT.
>
>
You shouldn't have to package everything up.
You say you've tried putting the jars in several different places. Do
you have multiple jars for azure still lying around? I wonder if you
might be seeing something truly wonky with the same jar being accessed
in two places.
The output is numbing, but
Just a little update on my concurrency issue.
The problem I was having was that under heavy load individual Solr
instances would be slow to respond eventually leading to flapping cluster
membership.
I tweaked a bunch of settings in Linux, Jetty, Solr and within my
application but in the end none
16 matches
Mail list logo