Hi again,
We are currently using Solr 7.3.1 and have a 8 shard collection. All our
TLOGs are in seperate machines & PULLs in others. Since not all shards are
in the same machine, the request will be distributed. However, we are
seeing that most of the 'distributed' parts of the requests are being
Hey,
I would like to get some feedback about LTS & EOL timeframes in Solr.
The Solr website states that "6.4.x" is a LTS version and "7.x" is the
current mayor version (https://lucene.apache.org/solr/community.html).
Question 1: Shouldn't it use "6.x", since version 6.6.5 is the latest
release
Hello All,
Need help on the error related to Solr indexing. We are using Solr 6.6.3 and
Nutch crawler 1.14. While indexing data to Solr we see errors as below
possible analysis error: Document contains at least one immense term in
field="content" (whose UTF8 encoding is longer than the max
Hey Shawn,
thanks a lot for your clarification, all questions answered.
Your message should indeed find it's way onto the community page.
Thanks.
Dan
Am 28.08.2018 um 13:18 schrieb Shawn Heisey:
> On 8/28/2018 2:59 AM, Dan Untenzu wrote:
>> I would like to get some feedback about LTS & EOL
On 8/28/2018 2:59 AM, Dan Untenzu wrote:
I would like to get some feedback about LTS & EOL timeframes in Solr.
The Solr website states that "6.4.x" is a LTS version and "7.x" is the
current mayor version (https://lucene.apache.org/solr/community.html).
Question 1: Shouldn't it use "6.x", since
On 8/28/2018 6:03 AM, kunhu0...@gmail.com wrote:
possible analysis error: Document contains at least one immense term in
field="content" (whose UTF8 encoding is longer than the max length 32766),
It's telling you exactly what is wrong.
The field named "content" is probably using a field class
Hi,
I am using Solr 7.4.0, and I would like to find out what is the best way to
train the model for the Solr Learning to Rank (LTR)?
So far these are the ways that I found:
- LibLinear, LibSVM
- LambdaMART
- RankLib
- NDCG
Regards,
Edwin
Patches welcome.
On Mon, Aug 27, 2018, 23:03 zhenyuan wei wrote:
> But this is not a common way to do so, I mean, nobody want to ADDREPLICA
> after collection was created.
>
> Erick Erickson 于2018年8月28日周二 下午1:24写道：
>
> > Every _replica_ can point to a different disk. When you do an
> >
Hi Ash,
Do you see all shard queries going to the TLOG replicas or “most” (are
there some going to the PULL replicas). You can confirm this by looking in
the logs for queries with “isShard=true” parameter. Are the PULL replicas
active (since you are using a load balancer I’m guessing you are not
Although I wrote that paragraph in the community page, it was never the
intention to give the impression of a formal LTS system, more meant as an
analogy to easier understand the release policy for that branch. So we should
probably avoid the term LTS altogether. What about LTP "Long Term
Bernd:
If you only knew how many times I've had the conversation "No, I can't
tell you what's best, you have to test with _your_ data on _your_
hardware with _your_ queries" ;)
I suspect, but have no real proof, that GC is the biggest difference,
Solr has we call "the laggard problem". Since
Hello, I am working on a project implementing Zookeeper and Solr cloud on a
cluster with 3 servers. I need to secure my zookeeper nodes so that they can
only communicate among themselves, I tried implementing ACLs according to the
documentation
Hi Emir,
I access the admin console through the ELB. I do NOT see any replication errors
in the new Slave's logs. I also double checked to make sure the connectivity
between the master and slaves exist. The only error I see in the new Slave log
is what I shared originally.
Thanks,
Zafar.
Hi Zafar,
Slaves are separate nodes and accessing admin console through ELB does not make
much sense since different requests will go to different nodes and that’s why
you sometimes see cores and other time it is empty. Since it is empty, it seems
that you did not define core(s) on this new
In case anyone else runs into this, I tracked it down. I had to force maven to
explicitly include all of it’s dependent jars in the plugin jar using the
assembly plugin in the pom like so:
maven-assembly-plugin
2.5.3
jar-with-dependencies
But this is not a common way to do so, I mean, nobody want to ADDREPLICA
after collection was created.
Erick Erickson 于2018年8月28日周二 下午1:24写道：
> Every _replica_ can point to a different disk. When you do an
> ADDREPLICA, then you can supply whatever path to the data
> you desire. And you can
Yes, I tested many cases.
As I already mentioned 3 Server as 3x3 SolrCloud cluster.
- 12 Mio. data records from our big single index
- always the same queries (SWD, german keyword norm data)
- Apache jmeter 3.1 for the load (separate server)
- Haproxy 1.6.11 with roundrobin (separate server)
- no
Hi Zafar,
How do you access admin console? Through ELB or you see this behaviour when
accessing admin console of a new slave? Do you see any replication related
errors in new slave’s logs? Did you check connectivity of a new slave and
master nodes?
Thanks,
Emir
--
Monitoring - Log Management -
Hi,
I am using Solr 7.4.0, and using LIBLINEAR to do the training for the LTR
model based on this example:
https://github.com/bloomberg/lucene-solr/blob/master-ltr/solr/contrib/ltr/example/README.md
However, I found that when I wanted to train for solr filter query with the
class SolrFeature, I
19 matches
Mail list logo
