Re: Unsubscribe me

[Thomas Corthals]

And if all else fails, set up a message rule to silently discard them.

Op wo 13 jul. 2022 om 08:44 schreef Michał Świątkowski
:

> Hi,
>
> To remove address from the list, send a message to
> users-unsubscr...@solr.apache.org
>
> Regards,
> Michal
>
> On 7/13/22 04:22, Gus Heck wrote:
> > Have you checked that the mails are actually going to the address you are
> > unsubscribing from? If you are getting mails forwarded from a prior
> address
> > you would need to send the unsubscribe from that address.
> >
> > On Tue, Jul 12, 2022 at 5:57 PM Brad Burke  wrote:
> >
> >> Ha.  Same here.  I have tried ever way I know how to send unsubscribe
> >> messages.  These emails never stop.
> >>
> >> On Tue, Jul 12, 2022 at 4:36 PM Jeryl Cook  wrote:
> >>
> >>> Good luck..Ive been trying to unsubscribe for years and cannot. But
> I've
> >>> accepted my fate.
> >>>
> >>> -jeryl cook
> >>>
> >>> On Tue, Jul 12, 2022, 4:29 PM Nicolas Franck
> >>>  wrote:
> >>>
>  Can someone unsubscribe me from this list?
> 
> 
> >
>

RE: Unsubscribe me

[Boitumelo Molekwa]

Also me please

-Original Message-
From: Nicolas Franck 
Sent: 12 July 2022 10:29 PM
To: users@solr.apache.org
Subject: Unsubscribe me


CAUTION: This email originates from outside of the organisation. Do not click 
on links or open attachments unless you recognise the sender and know that the 
content is safe.


Can someone unsubscribe me from this list?

- *** Disclaimer *** 
-
Important Notice:  This e-mail is subject to the e-mail disclaimer of the South 
African Reserve Bank, which can be viewed at:
 http://www.resbank.co.za/Disclaimer/Pages/SARB-Disclaimer.aspx
Should you be unable to access the link provided, 
kindly send an email to bstd-ict-serviced...@resbank.co.za
- *** Disclaimer *** 
-

Re: Unsubscribe me

[Dave]

To be clear I don’t want to unsubscribe 

> On Jul 13, 2022, at 5:18 AM, Boitumelo Molekwa 
>  wrote:
> 
> Also me please
> 
> -Original Message-
> From: Nicolas Franck 
> Sent: 12 July 2022 10:29 PM
> To: users@solr.apache.org
> Subject: Unsubscribe me
> 
> 
> CAUTION: This email originates from outside of the organisation. Do not click 
> on links or open attachments unless you recognise the sender and know that 
> the content is safe.
> 
> 
> Can someone unsubscribe me from this list?
> 
> - *** Disclaimer *** 
> -
> Important Notice:  This e-mail is subject to the e-mail disclaimer of the 
> South African Reserve Bank, which can be viewed at:
> http://www.resbank.co.za/Disclaimer/Pages/SARB-Disclaimer.aspx
> Should you be unable to access the link provided, 
> kindly send an email to bstd-ict-serviced...@resbank.co.za
> - *** Disclaimer *** 
> -
> 

Re: Large number of elements in multivalued field

[Ryan Yacyshyn]

Thanks Markus,

The field does not need to be returned in the response so setting stored to
false.

Regards,
Ryan




On Wed, Jul 13, 2022, 06:02 Markus Jelsma 
wrote:

> Hello Ryan,
>
> Solr should have no issues for indexing these kinds of documents,
> retrieving them is another thing. For multiValued a lot of
> datastructures are created when serializing the document, that is
> probably the problem.
>
> If you do not need the field returned, do not stored=true the field.
> If you do, how about making it not multiValued, but store all values
> using a delimiter. Use analysis to split on the delimiter so you can
> still search for it. When retrieving the document, it should just spit
> out a massive field.
>
> Such a large field will still take some time, but it should take less
> time and eat less memory than that many multiValued values.
> Deserializing should also take less time, imagine your browser neatly
> showing that many objects in XML format.
>
> Regards,
> Markus
>
> 2022-07-12 15:23 GMT+02:00, Ryan Yacyshyn :
> > Hi all,
> >
> > I have a data modelling question. A department of ours is indexing
> > companies and including a multivalued field in the doc to store a set of
> > tickers related to the company. Sounded fine at first until I saw one
> > document where the multivalued field had over 50,000 elements in it.
> There
> > are other documents that are storing even more than this because Solr
> will
> > hang and won't return the document.
> >
> > This is a *_ss field, and their query would be an exact match to one of
> the
> > values in this field to return the company name, eg:
> > ticker_fieldname_ss:"AAA NOE 12/31/21".
> >
> > I'm wondering what would be the best solution to index this data and
> search
> > for the ticker information on a company?
> >
> > One way I'm thinking of is rather than storing the ticker information as
> a
> > field on the company, have each ticker its own document with the
> fieldname
> > of the company.
> >
> > Would love to hear your thoughts on this.
> >
> > Thanks!
> >
> > Regards,
> > Ryan
> >
>

Solr Core Initialization Failure

[Bejoy Thankachan]

SolrCore Initialization Failures I have a 
3 node solr 8.11.1 setup (port 8983) with 3 node external zookeeper 3.7.1 (p 
2181). After I did a clean setup, I see Solr Core Initialization error in the 
admin console. The error is below. I have no idea how to avoid this error? Any 
help will be appreciated. solr error image


   solr: 
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException

   atom: 
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException

   tika: 
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException

   db: org.apache.solr.common.SolrException:org.apache.solr.common.SolrException



Here is the error from the log.

2022-07-13 02:57:58.734 ERROR 
(coreLoadExecutor-21-thread-2-processing-n:192.168.1.1:3001_solr) [c:db x:db] 
o.a.s.c.ZkController => org.apache.solr.common.SolrException: Could not find 
collection : db at 
org.apache.solr.common.cloud.ClusterState.getCollection(ClusterState.java:123) 
org.apache.solr.common.SolrException: Could not find collection : db at 
org.apache.solr.common.cloud.ClusterState.getCollection(ClusterState.java:123) 
~[?:?] at 
org.apache.solr.core.CoreContainer.repairCoreProperty(CoreContainer.java:2194) 
~[?:?] at 
org.apache.solr.cloud.ZkController.checkStateInZk(ZkController.java:1906) 
~[?:?] at 
org.apache.solr.cloud.ZkController.preRegister(ZkController.java:1843) ~[?:?] 
at 
org.apache.solr.core.CoreContainer.createFromDescriptor(CoreContainer.java:1443)
 ~[?:?] at 
org.apache.solr.core.CoreContainer.lambda$load$11(CoreContainer.java:873) 
~[?:?] at 
com.codahale.metrics.InstrumentedExecutorService$InstrumentedCallable.call(InstrumentedExecutorService.java:202)
 ~[metrics-core-4.1.5.jar:4.1.5] at 
java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_331] at 
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218)
 ~[?:?] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
~[?:1.8.0_331] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
~[?:1.8.0_331] at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_331] 
2022-07-13 02:57:58.740 ERROR 
(coreLoadExecutor-21-thread-2-processing-n:192.168.1.1:3001_solr) [c:solr 
x:solr] o.a.s.c.ZkController => org.apache.solr.common.SolrException: Could not 
find collection : solr at 
org.apache.solr.common.cloud.ClusterState.getCollection(ClusterState.java:123) 
org.apache.solr.common.SolrException: Could not find collection : solr at 
org.apache.solr.common.cloud.ClusterState.getCollection(ClusterState.java:123) 
~[?:?] at 
org.apache.solr.core.CoreContainer.repairCoreProperty(CoreContainer.java:2194) 
~[?:?] at 
org.apache.solr.cloud.ZkController.checkStateInZk(ZkController.java:1906) 
~[?:?] at 
org.apache.solr.cloud.ZkController.preRegister(ZkController.java:1843) ~[?:?] 
at 
org.apache.solr.core.CoreContainer.createFromDescriptor(CoreContainer.java:1443)
 ~[?:?] at 
org.apache.solr.core.CoreContainer.lambda$load$11(CoreContainer.java:873) 
~[?:?] at 
com.codahale.metrics.InstrumentedExecutorService$InstrumentedCallable.call(InstrumentedExecutorService.java:202)
 ~[metrics-core-4.1.5.jar:4.1.5] at 
java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_331] at 
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218)
 ~[?:?] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
~[?:1.8.0_331] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
~[?:1.8.0_331] at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_331] 
2022-07-13 02:57:58.741 ERROR 
(coreLoadExecutor-21-thread-2-processing-n:192.168.1.1:3001_solr) [c:tika 
x:tika] o.a.s.c.ZkController => org.apache.solr.common.SolrException: Could not 
find collection : tika at 
org.apache.solr.common.cloud.ClusterState.getCollection(ClusterState.java:123) 
org.apache.solr.common.SolrException: Could not find collection : tika at 
org.apache.solr.common.cloud.ClusterState.getCollection(ClusterState.java:123) 
~[?:?] at 
org.apache.solr.core.CoreContainer.repairCoreProperty(CoreContainer.java:2194) 
~[?:?] at 
org.apache.solr.cloud.ZkController.checkStateInZk(ZkController.java:1906) 
~[?:?] at 
org.apache.solr.cloud.ZkController.preRegister(ZkController.java:1843) ~[?:?] 
at 
org.apache.solr.core.CoreContainer.createFromDescriptor(CoreContainer.java:1443)
 ~[?:?] at 
org.apache.solr.core.CoreContainer.lambda$load$11(CoreContainer.java:873) 
~[?:?] at 
com.codahale.metrics.InstrumentedExecutorService$InstrumentedCallable.call(InstrumentedExecutorService.java:202)
 ~[metrics-core-4.1.5.jar:4.1.5] at 
java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_331] at 
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218)
 ~[?:?]

Re: Solr Core Initialization Failure

[Shawn Heisey]

On 7/13/22 14:39, Bejoy Thankachan wrote:

SolrCore Initialization Failures I have a 3 node 
solr 8.11.1 setup (port 8983) with 3 node external zookeeper 3.7.1 (p 2181). After I did a 
clean setup, I see Solr Core Initialization error in the admin console. The error is below. 
I have no idea how to avoid this error? Any help will be appreciated. solr error 
image


The following bits in the large amount of log data seem relevant:

Could not find collection : db
Could not find collection : solr
Could not find collection : tika
Could not find collection : mail
Could not find collection : atom

These are the names of the cores in the DIH example:

https://solr.apache.org/guide/8_5/uploading-structured-data-store-data-with-the-data-import-handler.html#solrs-dih-examples

It looks like you took a Solr install that was not running in cloud 
mode, with the five cores created by the DIH example, and asked it to 
start in cloud mode.  For each of the cores in that install, the error 
messages are telling you that the collection with the same name was not 
found in the cluster data from zookeeper.  Therefore it failed to start 
those cores.


I'm actually surprised that Solr didn't just completely delete the cores 
without notice.


Each Solr node in a new SolrCloud install must begin with no index 
cores.  SolrCloud works partly within Solr and partly within the cluster 
database that lives in ZK.


Thanks,
Shawn