idance. I saw that the file "
org/apache/solr/search/SolrIndexSearcher.java" has the metrics in them, but
got a bit lost from first glance.
If anyone has any information that could help me;
1. Replicate the issue
2. Explain what exactly does it mean when IndexReader is closed
I would be really grateful,
Kind Regards,
Richard Goodman
stance. If you
> have the capacity to upgrade your Solr version this will save you having to
> maintain the exporter separately. Since making this change the exporter has
> not missed a beat and we monitor around 100 Solr nodes.
>
> Good luck,
>
> Dwane
>
lso, would it bring up a question of having a better response
rather than a 500 status error if no metrics are available?
Kind regards,
--
Richard Goodman
lection_four_shard1_replica_p87",
"shard": "shard1",
"collection": "collection_four",
"state": "active",
"shard_name": "collection_four_shard1",
"num_shards": 6,
"type": "PULL"
},
"replica_t75": {
"core": "collection_four_shard1_replica_t75",
"shard": "shard1",
"collection": "collection_four",
"state": "active",
"shard_name": "collection_four_shard1",
"type": "TLOG",
"leader": "true"
}
}
Am I missing something to preserve replicationFactor for a collection, and
trying to make collections have 1 TLOG replica and 2 PULL replicas?
I tried adding the following
{"replicas": "<4", "shard":"#EACH", "node": "#ANY"}
However, still no luck
Equally, how would I then go about setting up triggers to only create a
PULL if a PULL goes down, and equally if the TLOG goes down? Would having a
trigger for each type be needed?
Any guidance on this would be greatly appreciated
Thanks,
--
Richard Goodman
thub.com/sematext/sematext-agent-integrations/tree/master/solr>
> >
> > You can also see some links to Solr metric related blog posts in this
> repo. If you find out that managing your own monitoring stack is
> overwhelming, you can try our Solr integration.
> >
Hey,
Sorry if this is the wrong group, I tried to email us...@infra.apache.org a
few weeks ago but haven't heard anything.
I am unable to log into my account, with it saying my password is
incorrect. But what is more odd is my name on the account has changed from
Richard Goodman to Alex Go
iated. If there isn't documentation for the API, then this would
also be something I'll look into help contributing with too.
Thanks,
--
Richard Goodman
helped, however,
it appears to be broken? I used a website archiver to retrieve the original
contents, but wasn't sure if it had been raised.
Thanks,
--
Richard Goodman|Data Infrastructure engineer
richa...@brandwatch.com
NEW YORK | BOSTON | BRIGHTON | LONDON | BERLIN |
" which
isn't allowed. However when going onto the /autoscaling/suggestions
endpoint, nothing is returned:
{
"responseHeader":{
"status":0,
"QTime":43848},
"suggestions":[],
"WARNING":"This response format is experimental. It is likely to change in
the future."}
I experimented by explicitly stating the racks that are present in the
cluster, i.e.
{
"replica": "#EQUAL",
"shard": "#EACH",
"sysprop.racklocation": ["/rack/001", "/rack/002", "/rack/003",
"/rack/004"]
}
With hopes that Solr would be able to use this to deduce where to place
violating replicas, however, this still doesn't work.
I was wondering if anyone had any similar experience with using system
properties for cluster policies, and how it affects the suggestions
endpoint, as I'm having difficulty of getting results from this.
Cheers,
Richard Goodman
So I managed to get this working by the following policy:
{"replica":"<2","shard":"#EACH","sysprop.racklocation": "#EACH"}
On Tue, 26 Mar 2019 at 14:03, Richard Goodman
wrote:
> Hi, I'm currently running into some trou
Hi, I'm currently running into some trouble trying to set up rack awareness
as a cluster policy.
I run my cluster with 3 way replication, currently a few collection-shards
have 4 replicas, which shows as violations under my current set policies:
{
"set-cluster-policy":[
{
"replica":"<2",
"shard":
11 matches
Mail list logo
