solr Metrics api

[akhil dutt]

Hi everyone,
  For the system cpu load and process cpu load, I sometimes see that
process cpu load is higher than system cpu load.I'm not sure in what cases
can it really be possible.Like in one case -
ProcessCpuLoad - 0.6908776706398165
SystemCpuLoad - 0.42642669943113387
 From what I understand from the definitions on OperatingSystemMXBean

page,
I dont think it is possible.Can it be an error in the way solr metrics api
is getting that , or can it happen in some cases?

Thanks

Re: Indexing data from multiple data sources

[Jörn Franke]

What does your Solr.log say? Any error ?

> Am 17.04.2020 um 20:22 schrieb RaviKiran Moola 
> :
> 
> 
> Hi,
> 
> Greetings!!!
> 
> We are working on indexing data from multiple data sources (MySQL & MSSQL) in 
> a single collection. We specified data source details like connection details 
> along with the required fields for both data sources in a single data config 
> file, along with specified required fields details in the managed schema and 
> here fetching the same columns from both data sources by specifying the 
> common “unique key”.
> 
> Unable to index the data from the data sources using solr.
> 
> Here I’m attaching the data config file and screenshot.
> 
> Data config file:
>  
>   url="jdbc:mysql://182.74.133.92:3306/ra_dev" user="devuser" 
> password="Welcome_009" batchSize="1" />  
>   driver="com.microsoft.sqlserver.jdbc.SQLServerDriver" 
> url="jdbc:sqlserver://182.74.133.92;databasename=BB_SOLR" user="matuser" 
> password="MatDev:07"/>   
>   
>   
>
> 
>   
>  
>   
>   
>   
>  
> 
> 
> 
> Thanks & Regards,
> Ravikiran Moola
> +91-9494924492
> 

RE: Indexing data from multiple data sources

[RaviKiran Moola]

Hi,

Greetings!!!

We are working on indexing data from multiple data sources (MySQL & MSSQL) in a 
single collection. We specified data source details like connection details 
along with the required fields for both data sources in a single data config 
file, along with specified required fields details in the managed schema and 
here fetching the same columns from both data sources by specifying the common 
“unique key”.

Unable to index the data from the data sources using solr.

Here I’m attaching the data config file and screenshot.

Data config file:

 
 
  
  
   
   
  
   
   
  

 




Thanks & Regards,

Ravikiran Moola

+91-9494924492

Re: 404 response from Schema API

[Shawn Heisey]

On 4/16/2020 10:07 AM, Mark H. Wood wrote:

I need to ask Solr 4.10 for the name of the unique key field of a
schema.  So far, no matter what I've done, Solr is returning a 404.

This works:

   curl 'https://toolshed.wood.net:8443/isw6_3/solr/statistics/select'

This gets a 404:

   curl 'https://toolshed.wood.net:8443/isw6_3/solr/statistics/schema/uniquekey'

So does this:

   curl 'https://toolshed.wood.net:8443/isw6_3/solr/statistics/schema'

We normally use the ClassicIndexSchemaFactory.  I tried switching to
ManagedIndexSchemaFactory but it made no difference.  Nothing is
logged for the failed requests.


From what I can see, the schema API handler was introduced in version 
5.0.  The SchemaHandler class exists in the released javadoc for the 5.0 
version, but not the 4.10 version.  You'll need a newer version of Solr.


Thanks,
Shawn

indexwriter shuts down

[j.s.]

hi

i am running a stand alone solr instance 7.3.1 that has been giving me 
errors recently. these are from an application log (not solr), but they 
appear to show that somehow the indexwriter gets shut down and show's over!


i am sure there are more clues in the logs, but i'm not sure where to 
find them. is this osme kinda known issue ... ?


any suggestions on ways forward? thx.


Error while indexing file with document id 
mod_assign-activity-88477-solrfile25611739: Exception writing document 
id mod_assign-activity-88477-solrfile25611739 to the index; possible 
analysis error$
Error while indexing file with document id 
mod_assign-activity-88477-solrfile25611741: Exception writing document 
id mod_assign-activity-88477-solrfile25611741 to the index; possible 
analysis error.

  Processed 4515 records containing 4376 documents, in 377.9 seconds.
... used 195019 dbqueries
... used 405.2789349556 seconds
Scheduled task failed: Global search indexing 
(core\task\search_index_task),org.apache.lucene.store

.AlreadyClosedException: this IndexWriter is closed
at 
org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:897)
at 
org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:911)
at 
org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:3422)
at 
org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:684)


(and on and on ...)

requesting help on auto scaling of solr

[saicharan.k...@spglobal.com]

Hello,

I am trying to add auto scaling for a cluster that is hosted on aws

I am using cluster policy as

{
"set-cluster-policy": [
{
"replica": "<2",
"shard": "#EACH",
"node": "#ANY"
}
]
}
Node-added-trigger

{
  "set-trigger": {
"name": "node_added_trigger",
"event": "nodeAdded",
"waitFor": "5s",
"preferredOperation": "ADDREPLICA"
  }
}

Node-lost-trigger as
{
  "set-trigger": {
"name": "node_lost_trigger",
"event": "nodeLost",
"waitFor": "120s",
"preferredOperation": "DELETENODE"
  }
}

When a node is terminated and new node gets added the replicas of lost node are 
not getting added to new node
Rather a replica of each shard is added on new node (10.24.76.89 is the new 
node )

[cid:image001.png@01D614CA.F11AE7F0]



What we expect is to add the replica of lost node on new node using autoscaling

Thank you,
charan




The information contained in this message is intended only for the recipient, 
and may be a confidential attorney-client communication or may otherwise be 
privileged and confidential and protected from disclosure. If the reader of 
this message is not the intended recipient, or an employee or agent responsible 
for delivering this message to the intended recipient, please be aware that any 
dissemination or copying of this communication is strictly prohibited. If you 
have received this communication in error, please immediately notify us by 
replying to the message and deleting it from your computer. S Global Inc. 
reserves the right, subject to applicable local law, to monitor, review and 
process the content of any electronic message or information sent to or from 
S Global Inc. e-mail addresses without informing the sender or recipient of 
the message. By sending electronic message or information to S Global Inc. 
e-mail addresses you, as the sender, are consenting to S Global Inc. 
processing any of your personal data therein.