Re: Basic Authentication problem

[Salmaan Rashid Syed]

My curl command works fine for querying, updating etc.

I don't think it is the fault of curl command.

I get the following error message when I tried to change the password of
solr-admin,








Error 403 Unauthorized request, Response code: 403



HTTP ERROR 403

Problem accessing /solr/admin/authentication. Reason:

Unauthorized request, Response code: 403






And if I give incorrect username and password, it states bad credentials
entered. So, I think the curl command is fine. There is some issue with
basic authentication.


Okay, One way around is to figure out how to convert my password into a
SHA256 (password + salt) and enter it in security.json file. But, I have no
idea how to generate the SHA256 equivalent of my password.


Any suggestions?



On Fri, Aug 2, 2019 at 10:55 AM Zheng Lin Edwin Yeo 
wrote:

> Hi Salmaan,
>
> Does your curl command works for other curl commands like normal querying?
> Or is it just not working when updating password and adding new users?
>
> Regards,
> Edwin
>
>
>
> On Fri, 2 Aug 2019 at 13:03, Salmaan Rashid Syed <
> salmaan.ras...@mroads.com>
> wrote:
>
> > Hi Zheng,
> >
> > I tried and it works. But, when I use the curl command to update password
> > or add new users it doesn't work.
> >
> > I don't know what is going wrong with curl command!
> >
> > Regards,
> > Salmaan
> >
> >
> > On Fri, Aug 2, 2019 at 8:26 AM Zheng Lin Edwin Yeo  >
> > wrote:
> >
> > > Have you tried to access the Solr Admin UI with your created user name
> > and
> > > password to see if it works?
> > >
> > > Regards,
> > > Edwin
> > >
> > > On Thu, 1 Aug 2019 at 19:51, Salmaan Rashid Syed <
> > > salmaan.ras...@mroads.com>
> > > wrote:
> > >
> > > > Hi Solr User,
> > > >
> > > > Please help me with my issue.
> > > >
> > > > I have enabled Solr basic authentication as shown in Solr
> > documentations.
> > > >
> > > > I have changed username from solr to solr-admin as follow
> > > >
> > > > {
> > > > "authentication":{
> > > >"blockUnknown": true,
> > > >"class":"solr.BasicAuthPlugin",
> > > >
> > > >
> > >
> "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> > > > Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> > > > },
> > > > "authorization":{
> > > >"class":"solr.RuleBasedAuthorizationPlugin",
> > > >"permissions":[{"name":"security-edit",
> > > >   "role":"admin"}],
> > > >"user-role":{"solr-admin":"admin"}
> > > > }}
> > > >
> > > > I am able to login to the page using the credentials
> > > solr-admin:SolrRocks.
> > > >
> > > > But, when I try to change the default password using the curl command
> > as
> > > > follows,
> > > >
> > > > curl --user solr-admin:SolrRocks
> > > > http://localhost:8983/solr/admin/authentication -H
> > > > 'Content-type:application/json' -d
> > '{"set-user":{"solr-admin":"s2019"}}'
> > > >
> > > >
> > > > I get the following error message,
> > > >
> > > >
> > > > 
> > > >
> > > > 
> > > >
> > > > 
> > > >
> > > > Error 403 Unauthorized request, Response code: 403
> > > >
> > > > 
> > > >
> > > > HTTP ERROR 403
> > > >
> > > > Problem accessing /solr/admin/authentication. Reason:
> > > >
> > > > Unauthorized request, Response code: 403
> > > >
> > > > 
> > > >
> > > > 
> > > >
> > > >
> > > > Please help.
> > > >
> > > > Regards,
> > > > Salmaan
> > > >
> > > >
> > > > On Thu, Aug 1, 2019 at 1:51 PM Salmaan Rashid Syed <
> > > > salmaan.ras...@mroads.com> wrote:
> > > >
> > > > > Small correction in the user-name. It is solr-admin everywhere.
> > > > >
> > > > > Hi Solr Users,
> > > > >
> > > > > I have enabled Solr basic authentication as shown in Solr
> > > documentations.
> > > > >
> > > > > I have changed username from solr to solr-admin as follow
> > > > >
> > > > > {
> > > > > "authentication":{
> > > > >"blockUnknown": true,
> > > > >"class":"solr.BasicAuthPlugin",
> > > > >
> > > > >
> > > >
> > "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> > > > > Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> > > > > },
> > > > > "authorization":{
> > > > >"class":"solr.RuleBasedAuthorizationPlugin",
> > > > >"permissions":[{"name":"security-edit",
> > > > >   "role":"admin"}],
> > > > >"user-role":{"solr-admin":"admin"}
> > > > > }}
> > > > >
> > > > > I am able to login to the page using the credentials
> > > > > mroads-solr-admin:SolrRocks.
> > > > >
> > > > > But, when I try to change the default password using the curl
> command
> > > as
> > > > > follows,
> > > > >
> > > > > curl --user solr-admin:SolrRocks
> > > > > http://localhost:8983/solr/admin/authentication -H
> > > > > 'Content-type:application/json' -d
> > > '{"set-user":{"solr-admin":"s2019"}}'
> > > > >
> > > > >
> > > > >
> > > > > I get the following error message,
> > > > >
> > > > >
> > > > > 
> > > > >
> > > > > 
> > > > >
> > > > > 
> > > > >
> > > > > Error 403 Unauthorized request, Response code: 403
> > > > >
> > > > > 
> > > > >
> > > > > HTTP ERROR 403
> > > > >
> > > > > 

Re: Basic Authentication problem

[Zheng Lin Edwin Yeo]

Hi Salmaan,

Does your curl command works for other curl commands like normal querying?
Or is it just not working when updating password and adding new users?

Regards,
Edwin



On Fri, 2 Aug 2019 at 13:03, Salmaan Rashid Syed 
wrote:

> Hi Zheng,
>
> I tried and it works. But, when I use the curl command to update password
> or add new users it doesn't work.
>
> I don't know what is going wrong with curl command!
>
> Regards,
> Salmaan
>
>
> On Fri, Aug 2, 2019 at 8:26 AM Zheng Lin Edwin Yeo 
> wrote:
>
> > Have you tried to access the Solr Admin UI with your created user name
> and
> > password to see if it works?
> >
> > Regards,
> > Edwin
> >
> > On Thu, 1 Aug 2019 at 19:51, Salmaan Rashid Syed <
> > salmaan.ras...@mroads.com>
> > wrote:
> >
> > > Hi Solr User,
> > >
> > > Please help me with my issue.
> > >
> > > I have enabled Solr basic authentication as shown in Solr
> documentations.
> > >
> > > I have changed username from solr to solr-admin as follow
> > >
> > > {
> > > "authentication":{
> > >"blockUnknown": true,
> > >"class":"solr.BasicAuthPlugin",
> > >
> > >
> > "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> > > Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> > > },
> > > "authorization":{
> > >"class":"solr.RuleBasedAuthorizationPlugin",
> > >"permissions":[{"name":"security-edit",
> > >   "role":"admin"}],
> > >"user-role":{"solr-admin":"admin"}
> > > }}
> > >
> > > I am able to login to the page using the credentials
> > solr-admin:SolrRocks.
> > >
> > > But, when I try to change the default password using the curl command
> as
> > > follows,
> > >
> > > curl --user solr-admin:SolrRocks
> > > http://localhost:8983/solr/admin/authentication -H
> > > 'Content-type:application/json' -d
> '{"set-user":{"solr-admin":"s2019"}}'
> > >
> > >
> > > I get the following error message,
> > >
> > >
> > > 
> > >
> > > 
> > >
> > > 
> > >
> > > Error 403 Unauthorized request, Response code: 403
> > >
> > > 
> > >
> > > HTTP ERROR 403
> > >
> > > Problem accessing /solr/admin/authentication. Reason:
> > >
> > > Unauthorized request, Response code: 403
> > >
> > > 
> > >
> > > 
> > >
> > >
> > > Please help.
> > >
> > > Regards,
> > > Salmaan
> > >
> > >
> > > On Thu, Aug 1, 2019 at 1:51 PM Salmaan Rashid Syed <
> > > salmaan.ras...@mroads.com> wrote:
> > >
> > > > Small correction in the user-name. It is solr-admin everywhere.
> > > >
> > > > Hi Solr Users,
> > > >
> > > > I have enabled Solr basic authentication as shown in Solr
> > documentations.
> > > >
> > > > I have changed username from solr to solr-admin as follow
> > > >
> > > > {
> > > > "authentication":{
> > > >"blockUnknown": true,
> > > >"class":"solr.BasicAuthPlugin",
> > > >
> > > >
> > >
> "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> > > > Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> > > > },
> > > > "authorization":{
> > > >"class":"solr.RuleBasedAuthorizationPlugin",
> > > >"permissions":[{"name":"security-edit",
> > > >   "role":"admin"}],
> > > >"user-role":{"solr-admin":"admin"}
> > > > }}
> > > >
> > > > I am able to login to the page using the credentials
> > > > mroads-solr-admin:SolrRocks.
> > > >
> > > > But, when I try to change the default password using the curl command
> > as
> > > > follows,
> > > >
> > > > curl --user solr-admin:SolrRocks
> > > > http://localhost:8983/solr/admin/authentication -H
> > > > 'Content-type:application/json' -d
> > '{"set-user":{"solr-admin":"s2019"}}'
> > > >
> > > >
> > > >
> > > > I get the following error message,
> > > >
> > > >
> > > > 
> > > >
> > > > 
> > > >
> > > > 
> > > >
> > > > Error 403 Unauthorized request, Response code: 403
> > > >
> > > > 
> > > >
> > > > HTTP ERROR 403
> > > >
> > > > Problem accessing /solr/admin/authentication. Reason:
> > > >
> > > > Unauthorized request, Response code: 403
> > > >
> > > > 
> > > >
> > > > 
> > > >
> > > >
> > > > Please help.
> > > >
> > > >
> > > > *Thanks and Regards,*
> > > > Salmaan Rashid Syed
> > > > +91 8978353445 | www.panna.ai |
> > > > 5550 Granite Pkwy, Suite #225, Plano TX-75024.
> > > > Cyber Gateways, Hi-tech City, Hyderabad, Telangana, India.
> > > >
> > > >
> > > >
> > > > On Thu, Aug 1, 2019 at 1:48 PM Salmaan Rashid Syed <
> > > > salmaan.ras...@mroads.com> wrote:
> > > >
> > > >> Hi Solr Users,
> > > >>
> > > >> I have enabled Solr basic authentication as shown in Solr
> > > documentations.
> > > >>
> > > >> I have changed username from solr to solr-admin as follow
> > > >>
> > > >> {
> > > >> "authentication":{
> > > >>"blockUnknown": true,
> > > >>"class":"solr.BasicAuthPlugin",
> > > >>
> > > >>
> > >
> "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> > > >> Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> > > >> },
> > > >> "authorization":{
> > > >>"class":"solr.RuleBasedAuthorizationPlugin",
> > > >>"permissions":[{"name":"security-edit",
> > > >>

Re: Basic Authentication problem

[Salmaan Rashid Syed]

Hi Zheng,

I tried and it works. But, when I use the curl command to update password
or add new users it doesn't work.

I don't know what is going wrong with curl command!

Regards,
Salmaan


On Fri, Aug 2, 2019 at 8:26 AM Zheng Lin Edwin Yeo 
wrote:

> Have you tried to access the Solr Admin UI with your created user name and
> password to see if it works?
>
> Regards,
> Edwin
>
> On Thu, 1 Aug 2019 at 19:51, Salmaan Rashid Syed <
> salmaan.ras...@mroads.com>
> wrote:
>
> > Hi Solr User,
> >
> > Please help me with my issue.
> >
> > I have enabled Solr basic authentication as shown in Solr documentations.
> >
> > I have changed username from solr to solr-admin as follow
> >
> > {
> > "authentication":{
> >"blockUnknown": true,
> >"class":"solr.BasicAuthPlugin",
> >
> >
> "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> > Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> > },
> > "authorization":{
> >"class":"solr.RuleBasedAuthorizationPlugin",
> >"permissions":[{"name":"security-edit",
> >   "role":"admin"}],
> >"user-role":{"solr-admin":"admin"}
> > }}
> >
> > I am able to login to the page using the credentials
> solr-admin:SolrRocks.
> >
> > But, when I try to change the default password using the curl command as
> > follows,
> >
> > curl --user solr-admin:SolrRocks
> > http://localhost:8983/solr/admin/authentication -H
> > 'Content-type:application/json' -d '{"set-user":{"solr-admin":"s2019"}}'
> >
> >
> > I get the following error message,
> >
> >
> > 
> >
> > 
> >
> > 
> >
> > Error 403 Unauthorized request, Response code: 403
> >
> > 
> >
> > HTTP ERROR 403
> >
> > Problem accessing /solr/admin/authentication. Reason:
> >
> > Unauthorized request, Response code: 403
> >
> > 
> >
> > 
> >
> >
> > Please help.
> >
> > Regards,
> > Salmaan
> >
> >
> > On Thu, Aug 1, 2019 at 1:51 PM Salmaan Rashid Syed <
> > salmaan.ras...@mroads.com> wrote:
> >
> > > Small correction in the user-name. It is solr-admin everywhere.
> > >
> > > Hi Solr Users,
> > >
> > > I have enabled Solr basic authentication as shown in Solr
> documentations.
> > >
> > > I have changed username from solr to solr-admin as follow
> > >
> > > {
> > > "authentication":{
> > >"blockUnknown": true,
> > >"class":"solr.BasicAuthPlugin",
> > >
> > >
> > "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> > > Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> > > },
> > > "authorization":{
> > >"class":"solr.RuleBasedAuthorizationPlugin",
> > >"permissions":[{"name":"security-edit",
> > >   "role":"admin"}],
> > >"user-role":{"solr-admin":"admin"}
> > > }}
> > >
> > > I am able to login to the page using the credentials
> > > mroads-solr-admin:SolrRocks.
> > >
> > > But, when I try to change the default password using the curl command
> as
> > > follows,
> > >
> > > curl --user solr-admin:SolrRocks
> > > http://localhost:8983/solr/admin/authentication -H
> > > 'Content-type:application/json' -d
> '{"set-user":{"solr-admin":"s2019"}}'
> > >
> > >
> > >
> > > I get the following error message,
> > >
> > >
> > > 
> > >
> > > 
> > >
> > > 
> > >
> > > Error 403 Unauthorized request, Response code: 403
> > >
> > > 
> > >
> > > HTTP ERROR 403
> > >
> > > Problem accessing /solr/admin/authentication. Reason:
> > >
> > > Unauthorized request, Response code: 403
> > >
> > > 
> > >
> > > 
> > >
> > >
> > > Please help.
> > >
> > >
> > > *Thanks and Regards,*
> > > Salmaan Rashid Syed
> > > +91 8978353445 | www.panna.ai |
> > > 5550 Granite Pkwy, Suite #225, Plano TX-75024.
> > > Cyber Gateways, Hi-tech City, Hyderabad, Telangana, India.
> > >
> > >
> > >
> > > On Thu, Aug 1, 2019 at 1:48 PM Salmaan Rashid Syed <
> > > salmaan.ras...@mroads.com> wrote:
> > >
> > >> Hi Solr Users,
> > >>
> > >> I have enabled Solr basic authentication as shown in Solr
> > documentations.
> > >>
> > >> I have changed username from solr to solr-admin as follow
> > >>
> > >> {
> > >> "authentication":{
> > >>"blockUnknown": true,
> > >>"class":"solr.BasicAuthPlugin",
> > >>
> > >>
> > "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> > >> Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> > >> },
> > >> "authorization":{
> > >>"class":"solr.RuleBasedAuthorizationPlugin",
> > >>"permissions":[{"name":"security-edit",
> > >>   "role":"admin"}],
> > >>"user-role":{"solr-admin":"admin"}
> > >> }}
> > >>
> > >> I am able to login to the page using the credentials
> > >> mroads-solr-admin:SolrRocks.
> > >>
> > >> But, when I try to change the default password using the curl command
> as
> > >> follows,
> > >>
> > >> curl --user mroads-solr-admin:SolrRocks
> > >> http://localhost:8983/solr/admin/authentication -H
> > >> 'Content-type:application/json' -d
> > '{"set-user":{"mroads-solr":"Mroads@2019
> > >> #"}}'
> > >>
> > >>
> > >>
> > >> I get the following error message,
> > >>
> > >>
> > >> 
> > >>
> > >> 
> > >>
> > >> 
> > >>
> 

Re: Indexing information on number of attachments and their names in EML file

[Zheng Lin Edwin Yeo]

Hi,

Does anyone knows if this can be done on the Solr side?
Or it has to be done on the Tika side?

Regards,
Edwin

On Thu, 1 Aug 2019 at 09:38, Zheng Lin Edwin Yeo 
wrote:

> Hi,
>
> Would like to check, Is there anyway which we can detect the number of
> attachments and their names during indexing of EML files in Solr, and index
> those information into Solr?
>
> Currently, Solr is able to use Tika and Tesseract OCR to extract the
> contents of the attachments. However, I could not find the information
> about the number of attachments in the EML file and what are their filename.
>
> I am using Solr 7.6.0 in production, and also trying out on the new Solr
> 8.2.0.
>
> Regards,
> Edwin
>

Re: Basic Authentication problem

[Zheng Lin Edwin Yeo]

Have you tried to access the Solr Admin UI with your created user name and
password to see if it works?

Regards,
Edwin

On Thu, 1 Aug 2019 at 19:51, Salmaan Rashid Syed 
wrote:

> Hi Solr User,
>
> Please help me with my issue.
>
> I have enabled Solr basic authentication as shown in Solr documentations.
>
> I have changed username from solr to solr-admin as follow
>
> {
> "authentication":{
>"blockUnknown": true,
>"class":"solr.BasicAuthPlugin",
>
>  "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> },
> "authorization":{
>"class":"solr.RuleBasedAuthorizationPlugin",
>"permissions":[{"name":"security-edit",
>   "role":"admin"}],
>"user-role":{"solr-admin":"admin"}
> }}
>
> I am able to login to the page using the credentials solr-admin:SolrRocks.
>
> But, when I try to change the default password using the curl command as
> follows,
>
> curl --user solr-admin:SolrRocks
> http://localhost:8983/solr/admin/authentication -H
> 'Content-type:application/json' -d '{"set-user":{"solr-admin":"s2019"}}'
>
>
> I get the following error message,
>
>
> 
>
> 
>
> 
>
> Error 403 Unauthorized request, Response code: 403
>
> 
>
> HTTP ERROR 403
>
> Problem accessing /solr/admin/authentication. Reason:
>
> Unauthorized request, Response code: 403
>
> 
>
> 
>
>
> Please help.
>
> Regards,
> Salmaan
>
>
> On Thu, Aug 1, 2019 at 1:51 PM Salmaan Rashid Syed <
> salmaan.ras...@mroads.com> wrote:
>
> > Small correction in the user-name. It is solr-admin everywhere.
> >
> > Hi Solr Users,
> >
> > I have enabled Solr basic authentication as shown in Solr documentations.
> >
> > I have changed username from solr to solr-admin as follow
> >
> > {
> > "authentication":{
> >"blockUnknown": true,
> >"class":"solr.BasicAuthPlugin",
> >
> >
> "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> > Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> > },
> > "authorization":{
> >"class":"solr.RuleBasedAuthorizationPlugin",
> >"permissions":[{"name":"security-edit",
> >   "role":"admin"}],
> >"user-role":{"solr-admin":"admin"}
> > }}
> >
> > I am able to login to the page using the credentials
> > mroads-solr-admin:SolrRocks.
> >
> > But, when I try to change the default password using the curl command as
> > follows,
> >
> > curl --user solr-admin:SolrRocks
> > http://localhost:8983/solr/admin/authentication -H
> > 'Content-type:application/json' -d '{"set-user":{"solr-admin":"s2019"}}'
> >
> >
> >
> > I get the following error message,
> >
> >
> > 
> >
> > 
> >
> > 
> >
> > Error 403 Unauthorized request, Response code: 403
> >
> > 
> >
> > HTTP ERROR 403
> >
> > Problem accessing /solr/admin/authentication. Reason:
> >
> > Unauthorized request, Response code: 403
> >
> > 
> >
> > 
> >
> >
> > Please help.
> >
> >
> > *Thanks and Regards,*
> > Salmaan Rashid Syed
> > +91 8978353445 | www.panna.ai |
> > 5550 Granite Pkwy, Suite #225, Plano TX-75024.
> > Cyber Gateways, Hi-tech City, Hyderabad, Telangana, India.
> >
> >
> >
> > On Thu, Aug 1, 2019 at 1:48 PM Salmaan Rashid Syed <
> > salmaan.ras...@mroads.com> wrote:
> >
> >> Hi Solr Users,
> >>
> >> I have enabled Solr basic authentication as shown in Solr
> documentations.
> >>
> >> I have changed username from solr to solr-admin as follow
> >>
> >> {
> >> "authentication":{
> >>"blockUnknown": true,
> >>"class":"solr.BasicAuthPlugin",
> >>
> >>
> "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> >> Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> >> },
> >> "authorization":{
> >>"class":"solr.RuleBasedAuthorizationPlugin",
> >>"permissions":[{"name":"security-edit",
> >>   "role":"admin"}],
> >>"user-role":{"solr-admin":"admin"}
> >> }}
> >>
> >> I am able to login to the page using the credentials
> >> mroads-solr-admin:SolrRocks.
> >>
> >> But, when I try to change the default password using the curl command as
> >> follows,
> >>
> >> curl --user mroads-solr-admin:SolrRocks
> >> http://localhost:8983/solr/admin/authentication -H
> >> 'Content-type:application/json' -d
> '{"set-user":{"mroads-solr":"Mroads@2019
> >> #"}}'
> >>
> >>
> >>
> >> I get the following error message,
> >>
> >>
> >> 
> >>
> >> 
> >>
> >> 
> >>
> >> Error 403 Unauthorized request, Response code: 403
> >>
> >> 
> >>
> >> HTTP ERROR 403
> >>
> >> Problem accessing /solr/admin/authentication. Reason:
> >>
> >> Unauthorized request, Response code: 403
> >>
> >> 
> >>
> >> 
> >>
> >>
> >> Please help.
> >>
> >>
> >>
> >> *Thanks and Regards,*
> >> Salmaan Rashid Syed
> >> +91 8978353445 | www.panna.ai |
> >> 5550 Granite Pkwy, Suite #225, Plano TX-75024.
> >> Cyber Gateways, Hi-tech City, Hyderabad, Telangana, India.
> >>
> >>
> >
>

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Zheng Lin Edwin Yeo]

Yes, I tried with space and the same error occurs.

I have also tried to put * , but I am getting the same error as well.
4lw.commands.whitelist=*

Regards,
Edwin

On Thu, 1 Aug 2019 at 21:34, Jörn Franke  wrote:

> Spaces did not change the situation. In standalone it works without spaces
> and the issue is only if there is an ensemble. I checked all ZK nodes have
> the statement and have been restarted .
>
> So issue pics there for a ZK Ensemble only in admin UI. I will create
> tonight a JIRA if no one creates it before
>
> > Am 01.08.2019 um 12:58 schrieb Erick Erickson :
> >
> > The issue was only cosmetic in the sense that the admin UI was the only
> thing that was affected,
> > not other Solr functions when I was working on this.
> >
> > Please check a few things:
> >
> > 1> be absolutely sure that you’ve added this in all your zoo.cfg files
> >
> > 2> the example on the ZooKeeper website has spaces, could you try that
> just to cover all bases? Stranger things have happened…
> >
> > 4lw.commands.whitelist=mntr, ruok, conf
> > not
> > 4lw.commands.whitelist=mntr,ruok,conf
> >
> > 3> if <1> and <2> don’t work, what happens if you start your ZooKeepers
> with
> > -Dzookeeper.4lw.commands.whitelist=….
> >
> > If it’s not <1> or <2>, please raise a JIRA.
> >
> > Best,
> > Erick
> >
> > Also, see: SOLR-13502 (no work has been done on this yet)
> >
> >> On Aug 1, 2019, at 6:05 AM, Jörn Franke  wrote:
> >>
> >> For me:
> >> * ZK stand-alone mode - no issues
> >> * ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI (I
> see the same error message), but aside this Solr is working fine
> >>
> >>
> >>
> >>> Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo <
> edwinye...@gmail.com>:
> >>>
> >>> Hi Jörn,
> >>> Thank you for your reply.
> >>>
> >>> I have encountered problem when I tried to create a collection with
> this
> >>> new version of ZooKeeper. You can find my Solr log file here:
> >>> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> >>>
> >>> Does it work perfectly at your side for creating collections and
> indexing
> >>> even when running ZooKeeper ensemble?
> >>>
> >>> Regards,
> >>> Edwin
> >>>
> >>>
>  On Thu, 1 Aug 2019 at 17:39, Jörn Franke 
> wrote:
> 
>  I confirm the issue.
> 
>  Interestingly it does not happen with ZK standalone, but only in a ZK
>  Ensemble.
> 
>  It seems to be mainly cosmetic in the admin UI because Solr appears to
>  function normally.
> 
> > Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo <
> edwinye...@gmail.com
> > :
> >
> > Yes. You can get my full solr.log from the link below. The error is
> there
> > when I tried to create collection1 (around line 170 to 300) .
> >
> > https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> >
> > Regards,
> > Edwin
> >
> >
> >> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
>  wrote:
> >>
> >> Please look for the full log file solr.log in your Solr server, and
>  share
> >> it via some file sharing service or gist or similar for us to be
> able to
> >> decipher the collection create error.
> >>
> >> --
> >> Jan Høydahl, search solution architect
> >> Cominvent AS - www.cominvent.com
> >>
> >>> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
>  edwinye...@gmail.com
> >>> :
> >>>
> >>> Hi,
> >>>
> >>> Regarding the issue, I have tried to put the following in zoo.cfg
> under
> >>> ZooKeeper:
> >>> 4lw.commands.whitelist=mntr,conf,ruok
> >>>
> >>> But it is still showing this error.
> >>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
>  zookeeper
> >>> configuration file."*
> >>>
> >>> As I am using SolrCloud, the collection config can still be loaded
> to
> >>> ZooKeeper as per normal. But if I tried to create a collection, I
> will
> >> get
> >>> the following error:
> >>>
> >>> {
> >>> "responseHeader":{
> >>> "status":400,
> >>> "QTime":686},
> >>> "failure":{
> >>> "192.168.1.2:8983
> >> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
> >>> occurred when talking to server at:http://192.168.1.2:8983/solr;,
> >>> "192.168.1.2:8984
> >> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
> >>> occurred when talking to server at:http://192.168.1.2:8984/solr"},
> >>> "Operation create caused
> >>>
> >>
> 
> exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
> >>> Underlying core creation failed while creating collection:
>  collection1",
> >>> "exception":{f
> >>> "msg":"Underlying core creation failed while creating collection:
> >>> collection1",
> >>> "rspCode":400},
> >>> "error":{
> >>> "metadata":[
> >>>  "error-class","org.apache.solr.common.SolrException",
> >>>  

Re: Solr on HDFS

[Angie Rabelero]

I don’t think you’re using claudera or ambari, but ambari has an option to 
delete the locks. This seems more a configuration/architecture isssue than a 
realibility issue. You may want to spin up an alias while you bring down, clear 
locks and directories, recreate and index the affected collection, while you 
work your other isues.

On Aug 1, 2019, at 16:40, Joe Obernberger  wrote:

Been using Solr on HDFS for a while now, and I'm seeing an issue with 
redundancy/reliability.  If a server goes down, when it comes back up, it will 
never recover because of the lock files in HDFS. That solr node needs to be 
brought down manually, the lock files deleted, and then brought back up.  At 
that point, it appears to copy all the data for its replicas.  If the index is 
large, and new data is being indexed, in some cases it will never recover. The 
replication retries over and over.

How can we make a reliable Solr Cloud cluster when using HDFS that can handle 
servers coming and going?

Thank you!

-Joe

Solr on HDFS

[Joe Obernberger]

Been using Solr on HDFS for a while now, and I'm seeing an issue with 
redundancy/reliability.  If a server goes down, when it comes back up, 
it will never recover because of the lock files in HDFS. That solr node 
needs to be brought down manually, the lock files deleted, and then 
brought back up.  At that point, it appears to copy all the data for its 
replicas.  If the index is large, and new data is being indexed, in some 
cases it will never recover. The replication retries over and over.


How can we make a reliable Solr Cloud cluster when using HDFS that can 
handle servers coming and going?


Thank you!

-Joe

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Jan Høydahl]

Also try /admin/zookeeper/status endpoint in solr manually and see if you get a 
decent response, if not check error in logs.

Jan Høydahl

> 1. aug. 2019 kl. 20:25 skrev Jörn Franke :
> 
> here you go:
> https://issues.apache.org/jira/browse/SOLR-13672
> 
> I will check tomorrow Telnet, but I am not so optimistic it is the root
> cause, because this I observed already during rolling upgrade where one
> node had 3.5.5 and the other 3.4.14. They are all now on 3.5.5.
> Do you have a pointer to the code. Maybe I spot something or can do further
> tests based on it.
> 
>> On Thu, Aug 1, 2019 at 3:59 PM Jan Høydahl  wrote:
>> 
>> Yes please do. I made the ZkStatus UI and it works by letting the solr
>> node that Admin UI is connected to do 4LW commands to each ZK node and then
>> concatenate the results.
>> 
>> You could try to invoke each of the 4LW commands manually on each ZK
>> server using telnet, and see if that succeeds for all hosts and commands..
>> 
>> telnet host.name 2181
>> conf
>> 
>> Jan Høydahl
>> 
>>> 1. aug. 2019 kl. 15:34 skrev Jörn Franke :
>>> 
>>> Spaces did not change the situation. In standalone it works without
>> spaces and the issue is only if there is an ensemble. I checked all ZK
>> nodes have the statement and have been restarted .
>>> 
>>> So issue pics there for a ZK Ensemble only in admin UI. I will create
>> tonight a JIRA if no one creates it before
>>> 
 Am 01.08.2019 um 12:58 schrieb Erick Erickson >> :
 
 The issue was only cosmetic in the sense that the admin UI was the only
>> thing that was affected,
 not other Solr functions when I was working on this.
 
 Please check a few things:
 
 1> be absolutely sure that you’ve added this in all your zoo.cfg files
 
 2> the example on the ZooKeeper website has spaces, could you try that
>> just to cover all bases? Stranger things have happened…
 
 4lw.commands.whitelist=mntr, ruok, conf
 not
 4lw.commands.whitelist=mntr,ruok,conf
 
 3> if <1> and <2> don’t work, what happens if you start your ZooKeepers
>> with
 -Dzookeeper.4lw.commands.whitelist=….
 
 If it’s not <1> or <2>, please raise a JIRA.
 
 Best,
 Erick
 
 Also, see: SOLR-13502 (no work has been done on this yet)
 
> On Aug 1, 2019, at 6:05 AM, Jörn Franke  wrote:
> 
> For me:
> * ZK stand-alone mode - no issues
> * ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI
>> (I see the same error message), but aside this Solr is working fine
> 
> 
> 
>> Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo <
>> edwinye...@gmail.com>:
>> 
>> Hi Jörn,
>> Thank you for your reply.
>> 
>> I have encountered problem when I tried to create a collection with
>> this
>> new version of ZooKeeper. You can find my Solr log file here:
>> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
>> 
>> Does it work perfectly at your side for creating collections and
>> indexing
>> even when running ZooKeeper ensemble?
>> 
>> Regards,
>> Edwin
>> 
>> 
>>> On Thu, 1 Aug 2019 at 17:39, Jörn Franke 
>> wrote:
>>> 
>>> I confirm the issue.
>>> 
>>> Interestingly it does not happen with ZK standalone, but only in a ZK
>>> Ensemble.
>>> 
>>> It seems to be mainly cosmetic in the admin UI because Solr appears
>> to
>>> function normally.
>>> 
 Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo <
>> edwinye...@gmail.com
 :
 
 Yes. You can get my full solr.log from the link below. The error is
>> there
 when I tried to create collection1 (around line 170 to 300) .
 
 https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
 
 Regards,
 Edwin
 
 
> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
>>> wrote:
> 
> Please look for the full log file solr.log in your Solr server, and
>>> share
> it via some file sharing service or gist or similar for us to be
>> able to
> decipher the collection create error.
> 
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
> 
>> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
>>> edwinye...@gmail.com
>> :
>> 
>> Hi,
>> 
>> Regarding the issue, I have tried to put the following in zoo.cfg
>> under
>> ZooKeeper:
>> 4lw.commands.whitelist=mntr,conf,ruok
>> 
>> But it is still showing this error.
>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
>>> zookeeper
>> configuration file."*
>> 
>> As I am using SolrCloud, the collection config can still be
>> loaded to
>> ZooKeeper as per normal. But if I tried to create a collection, I
>> will
> get

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Jan Høydahl]

https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/handler/admin/ZookeeperStatusHandler.java

Jan Høydahl

> 1. aug. 2019 kl. 20:25 skrev Jörn Franke :
> 
> here you go:
> https://issues.apache.org/jira/browse/SOLR-13672
> 
> I will check tomorrow Telnet, but I am not so optimistic it is the root
> cause, because this I observed already during rolling upgrade where one
> node had 3.5.5 and the other 3.4.14. They are all now on 3.5.5.
> Do you have a pointer to the code. Maybe I spot something or can do further
> tests based on it.
> 
>> On Thu, Aug 1, 2019 at 3:59 PM Jan Høydahl  wrote:
>> 
>> Yes please do. I made the ZkStatus UI and it works by letting the solr
>> node that Admin UI is connected to do 4LW commands to each ZK node and then
>> concatenate the results.
>> 
>> You could try to invoke each of the 4LW commands manually on each ZK
>> server using telnet, and see if that succeeds for all hosts and commands..
>> 
>> telnet host.name 2181
>> conf
>> 
>> Jan Høydahl
>> 
>>> 1. aug. 2019 kl. 15:34 skrev Jörn Franke :
>>> 
>>> Spaces did not change the situation. In standalone it works without
>> spaces and the issue is only if there is an ensemble. I checked all ZK
>> nodes have the statement and have been restarted .
>>> 
>>> So issue pics there for a ZK Ensemble only in admin UI. I will create
>> tonight a JIRA if no one creates it before
>>> 
 Am 01.08.2019 um 12:58 schrieb Erick Erickson >> :
 
 The issue was only cosmetic in the sense that the admin UI was the only
>> thing that was affected,
 not other Solr functions when I was working on this.
 
 Please check a few things:
 
 1> be absolutely sure that you’ve added this in all your zoo.cfg files
 
 2> the example on the ZooKeeper website has spaces, could you try that
>> just to cover all bases? Stranger things have happened…
 
 4lw.commands.whitelist=mntr, ruok, conf
 not
 4lw.commands.whitelist=mntr,ruok,conf
 
 3> if <1> and <2> don’t work, what happens if you start your ZooKeepers
>> with
 -Dzookeeper.4lw.commands.whitelist=….
 
 If it’s not <1> or <2>, please raise a JIRA.
 
 Best,
 Erick
 
 Also, see: SOLR-13502 (no work has been done on this yet)
 
> On Aug 1, 2019, at 6:05 AM, Jörn Franke  wrote:
> 
> For me:
> * ZK stand-alone mode - no issues
> * ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI
>> (I see the same error message), but aside this Solr is working fine
> 
> 
> 
>> Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo <
>> edwinye...@gmail.com>:
>> 
>> Hi Jörn,
>> Thank you for your reply.
>> 
>> I have encountered problem when I tried to create a collection with
>> this
>> new version of ZooKeeper. You can find my Solr log file here:
>> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
>> 
>> Does it work perfectly at your side for creating collections and
>> indexing
>> even when running ZooKeeper ensemble?
>> 
>> Regards,
>> Edwin
>> 
>> 
>>> On Thu, 1 Aug 2019 at 17:39, Jörn Franke 
>> wrote:
>>> 
>>> I confirm the issue.
>>> 
>>> Interestingly it does not happen with ZK standalone, but only in a ZK
>>> Ensemble.
>>> 
>>> It seems to be mainly cosmetic in the admin UI because Solr appears
>> to
>>> function normally.
>>> 
 Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo <
>> edwinye...@gmail.com
 :
 
 Yes. You can get my full solr.log from the link below. The error is
>> there
 when I tried to create collection1 (around line 170 to 300) .
 
 https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
 
 Regards,
 Edwin
 
 
> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
>>> wrote:
> 
> Please look for the full log file solr.log in your Solr server, and
>>> share
> it via some file sharing service or gist or similar for us to be
>> able to
> decipher the collection create error.
> 
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
> 
>> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
>>> edwinye...@gmail.com
>> :
>> 
>> Hi,
>> 
>> Regarding the issue, I have tried to put the following in zoo.cfg
>> under
>> ZooKeeper:
>> 4lw.commands.whitelist=mntr,conf,ruok
>> 
>> But it is still showing this error.
>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
>>> zookeeper
>> configuration file."*
>> 
>> As I am using SolrCloud, the collection config can still be
>> loaded to
>> ZooKeeper as per normal. But if I tried to create a collection, I
>> will
> get

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Jörn Franke]

here you go:
https://issues.apache.org/jira/browse/SOLR-13672

I will check tomorrow Telnet, but I am not so optimistic it is the root
cause, because this I observed already during rolling upgrade where one
node had 3.5.5 and the other 3.4.14. They are all now on 3.5.5.
Do you have a pointer to the code. Maybe I spot something or can do further
tests based on it.

On Thu, Aug 1, 2019 at 3:59 PM Jan Høydahl  wrote:

> Yes please do. I made the ZkStatus UI and it works by letting the solr
> node that Admin UI is connected to do 4LW commands to each ZK node and then
> concatenate the results.
>
> You could try to invoke each of the 4LW commands manually on each ZK
> server using telnet, and see if that succeeds for all hosts and commands..
>
> telnet host.name 2181
> conf
>
> Jan Høydahl
>
> > 1. aug. 2019 kl. 15:34 skrev Jörn Franke :
> >
> > Spaces did not change the situation. In standalone it works without
> spaces and the issue is only if there is an ensemble. I checked all ZK
> nodes have the statement and have been restarted .
> >
> > So issue pics there for a ZK Ensemble only in admin UI. I will create
> tonight a JIRA if no one creates it before
> >
> >> Am 01.08.2019 um 12:58 schrieb Erick Erickson  >:
> >>
> >> The issue was only cosmetic in the sense that the admin UI was the only
> thing that was affected,
> >> not other Solr functions when I was working on this.
> >>
> >> Please check a few things:
> >>
> >> 1> be absolutely sure that you’ve added this in all your zoo.cfg files
> >>
> >> 2> the example on the ZooKeeper website has spaces, could you try that
> just to cover all bases? Stranger things have happened…
> >>
> >> 4lw.commands.whitelist=mntr, ruok, conf
> >> not
> >> 4lw.commands.whitelist=mntr,ruok,conf
> >>
> >> 3> if <1> and <2> don’t work, what happens if you start your ZooKeepers
> with
> >> -Dzookeeper.4lw.commands.whitelist=….
> >>
> >> If it’s not <1> or <2>, please raise a JIRA.
> >>
> >> Best,
> >> Erick
> >>
> >> Also, see: SOLR-13502 (no work has been done on this yet)
> >>
> >>> On Aug 1, 2019, at 6:05 AM, Jörn Franke  wrote:
> >>>
> >>> For me:
> >>> * ZK stand-alone mode - no issues
> >>> * ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI
> (I see the same error message), but aside this Solr is working fine
> >>>
> >>>
> >>>
>  Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo <
> edwinye...@gmail.com>:
> 
>  Hi Jörn,
>  Thank you for your reply.
> 
>  I have encountered problem when I tried to create a collection with
> this
>  new version of ZooKeeper. You can find my Solr log file here:
>  https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> 
>  Does it work perfectly at your side for creating collections and
> indexing
>  even when running ZooKeeper ensemble?
> 
>  Regards,
>  Edwin
> 
> 
> > On Thu, 1 Aug 2019 at 17:39, Jörn Franke 
> wrote:
> >
> > I confirm the issue.
> >
> > Interestingly it does not happen with ZK standalone, but only in a ZK
> > Ensemble.
> >
> > It seems to be mainly cosmetic in the admin UI because Solr appears
> to
> > function normally.
> >
> >> Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo <
> edwinye...@gmail.com
> >> :
> >>
> >> Yes. You can get my full solr.log from the link below. The error is
> there
> >> when I tried to create collection1 (around line 170 to 300) .
> >>
> >> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> >>
> >> Regards,
> >> Edwin
> >>
> >>
> >>> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
> > wrote:
> >>>
> >>> Please look for the full log file solr.log in your Solr server, and
> > share
> >>> it via some file sharing service or gist or similar for us to be
> able to
> >>> decipher the collection create error.
> >>>
> >>> --
> >>> Jan Høydahl, search solution architect
> >>> Cominvent AS - www.cominvent.com
> >>>
>  31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
> > edwinye...@gmail.com
>  :
> 
>  Hi,
> 
>  Regarding the issue, I have tried to put the following in zoo.cfg
> under
>  ZooKeeper:
>  4lw.commands.whitelist=mntr,conf,ruok
> 
>  But it is still showing this error.
>  *"Errors: - membership: Check 4lq.commands.whitelist setting in
> > zookeeper
>  configuration file."*
> 
>  As I am using SolrCloud, the collection config can still be
> loaded to
>  ZooKeeper as per normal. But if I tried to create a collection, I
> will
> >>> get
>  the following error:
> 
>  {
>  "responseHeader":{
>  "status":400,
>  "QTime":686},
>  "failure":{
>  "192.168.1.2:8983
> >>>
> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>  occurred 

Re: SolrCloud recommended I/O RAID level

[Erick Erickson]

Yes, I’m exactly talking about the idea of someone pulling the plug on one of 
your machines. RAID doesn’t help you at all with that.

10M docs/shard is pretty low actually, depending on the characteristics of docs 
of course. I’ve ween 10M docs strain things. I’ve seen 300M docs fit in 16G 
heap. My personal straw-man starting point is 50M docs/shard. You have to test. 
Old but still valid: 
https://lucidworks.com/post/sizing-hardware-in-the-abstract-why-we-dont-have-a-definitive-answer/

bq. Will additional replicas will assist with QPS

It Depends (tm). The article I linked above will help you answer the question, 
the only way I know of to answer definitively is to stress-test on a small (2 
nodes will do) cluster. Obviously if you’ve maxed out all your CPUs with no 
replicas, adding more replicas won’t help. But first you have to convince me 
that you’re maxing out all your CPUs.

Test, test, test.

Best,
Erick

> On Aug 1, 2019, at 7:35 AM, Kaminski, Adi  wrote:
> 
> Hi Erick,
> 
> Thanks for the detailed explanation, much appreciated.
> 
> 
> 
> Regarding #1 reason you have mentioned - but if RAID10 is chosen per Shawn's 
> suggestion, then we should be protected, no ? Unless you mean the whole 
> server is not available
> and not specific disk of configured RAID10.
> 
> 
> 
> Regarding #2 reason you have mentioned -
> 
> ·   If we’re having 7 Solr node/servers as part of SolrCloud cluster, 
> with 48 vCPU in each server (so in total ~336 vCPU in total)
> 
> ·   And we are talking about 2-3.2B of Solr docs distributed on this 
> cluster
> 
> ·   And assuming that each shard will handled 10M Solr docs in average 
> (that what we saw is some forums as basic “rule of thumb”)
> 
> ·   Questions:
> 
> o   Will additional replicas will assist with QPS ? As we will basically are 
> having ratio of 1 vCPU per 1 shard (the mster replica)
> 
> o   Wouldn’t additional replicas will overclock per total amout of vCPUs, and 
> actually cause delays in queries and lower QPS ?
> 
> 
> 
> Thanks,
> 
> Adi
> 
> 
> 
> -Original Message-
> From: Erick Erickson 
> Sent: Thursday, August 1, 2019 2:03 PM
> To: solr-user@lucene.apache.org
> Subject: Re: SolrCloud recommended I/O RAID level
> 
> 
> 
> “why would I need a replication factor of 2….”
> 
> 
> 
> Two reasons:
> 
> 
> 
> 1> assuming your replicas are located on different physical machines, you can 
> lose one and still keep on running. RAID won’t help if the machine dies.
> 
> 
> 
> 2> capacity. Depending on your query load, having more than one replica 
> distributes query loads across multiple Solr instances, increasing the QPS 
> you can handle.
> 
> 
> 
> If you don’t care about either of those issues, then no reason.
> 
> 
> 
> Best,
> 
> Erick
> 
> 
> 
>> On Aug 1, 2019, at 2:11 AM, Kaminski, Adi 
>> mailto:adi.kamin...@verint.com>> wrote:
> 
>> 
> 
>> Hi Shawn,
> 
>> Thanks for your reply, fully agree with your comments, it clarifies more the 
>> need of RAID10 in this case.
> 
>> 
> 
>> One additional follow-up question - in case we follow this guidelines
> 
>> and having RAID10 (which leaves us with effective capacity of 50%),
> 
>> why would I need replication factor of 2 in our SolrCloud core/collection ? 
>> Won't it be double protection layer, while the IO layer mirroring of RAID10 
>> actually brings the value, and no need to copy anything when we have IO 
>> failures ?
> 
>> 
> 
>> Thanks,
> 
>> Adi
> 
>> 
> 
>> -Original Message-
> 
>> From: Shawn Heisey mailto:apa...@elyograg.org>>
> 
>> Sent: Tuesday, July 30, 2019 9:44 PM
> 
>> To: solr-user@lucene.apache.org
> 
>> Subject: Re: SolrCloud recommended I/O RAID level
> 
>> 
> 
>> On 7/30/2019 12:12 PM, Kaminski, Adi wrote:
> 
>>> Indeed RAID10 with both mirroring and striping should satisfy the
> 
>>> need, but per some benchmarks in the network there is still an impact
> 
>>> on write performance on it compared to RAID0 which is considered as
> 
>>> much better (attaching a table that summarizes different RAID levels
> 
>>> and their pros/cons and capacity ratio).
> 
>> 
> 
>> RAID10 offers the best combination of performance and reliability.
> 
>> RAID0 might beat it *slightly* on performance, but if ANY drive fails on 
>> RAID0, the entire volume is lost.
> 
>> 
> 
>>> If we have ~200-320 shards spread by our 7 Solr node servers (part of
> 
>>> SolrCloud cluster) on single core/collection configured with
> 
>>> replication factor 2, shouldn't it supply applicative level
> 
>>> redundancy of indexed data ?
> 
>> 
> 
>> Yes, you could rely on Solr alone for data redundancy.  But if there's a 
>> drive failure, do you REALLY want to be single-stranded for the time it 
>> takes to rebuild the entire server and copy data?  That's what you would end 
>> up doing if you choose RAID0.
> 
>> 
> 
>> It is true that RAID1 or RAID10 means you have to buy double your usable 
>> capacity.  I would argue that drives are cheap and will cost 

RE: Basic Authentication problem

[Oakley, Craig (NIH/NLM/NCBI) [C]]

The hash value 
"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="
 is based on both the plain text password AND the plain test login. Since 
"solr" is not the same string as "solr-admin", the password will not work. If 
the only authorization in security.json is restricting security-edit, then you 
can do anything else with any password, or with no password.

What you can do is setup the security.json file as specified in the Reference 
Guide (whence you got the hash of the login and password), then use the default 
solr login to run your set-user (to add the solr-admin user alongside the 
existing solr login), then use the default solr login to run 
{"set-user-role":{"solr-admin":["security-edit"]}}, and then (when you are sure 
things are correctly setup for solr-admin) drop the default solr login

-Original Message-
From: Salmaan Rashid Syed  
Sent: Thursday, August 01, 2019 7:51 AM
To: solr-user@lucene.apache.org
Subject: Re: Basic Authentication problem

Hi Solr User,

Please help me with my issue.

I have enabled Solr basic authentication as shown in Solr documentations.

I have changed username from solr to solr-admin as follow

{
"authentication":{
   "blockUnknown": true,
   "class":"solr.BasicAuthPlugin",

 "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
},
"authorization":{
   "class":"solr.RuleBasedAuthorizationPlugin",
   "permissions":[{"name":"security-edit",
  "role":"admin"}],
   "user-role":{"solr-admin":"admin"}
}}

I am able to login to the page using the credentials solr-admin:SolrRocks.

But, when I try to change the default password using the curl command as
follows,

curl --user solr-admin:SolrRocks
http://localhost:8983/solr/admin/authentication -H
'Content-type:application/json' -d '{"set-user":{"solr-admin":"s2019"}}'


I get the following error message,








Error 403 Unauthorized request, Response code: 403



HTTP ERROR 403

Problem accessing /solr/admin/authentication. Reason:

Unauthorized request, Response code: 403






Please help.

Regards,
Salmaan


On Thu, Aug 1, 2019 at 1:51 PM Salmaan Rashid Syed <
salmaan.ras...@mroads.com> wrote:

> Small correction in the user-name. It is solr-admin everywhere.
>
> Hi Solr Users,
>
> I have enabled Solr basic authentication as shown in Solr documentations.
>
> I have changed username from solr to solr-admin as follow
>
> {
> "authentication":{
>"blockUnknown": true,
>"class":"solr.BasicAuthPlugin",
>
>  "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> },
> "authorization":{
>"class":"solr.RuleBasedAuthorizationPlugin",
>"permissions":[{"name":"security-edit",
>   "role":"admin"}],
>"user-role":{"solr-admin":"admin"}
> }}
>
> I am able to login to the page using the credentials
> mroads-solr-admin:SolrRocks.
>
> But, when I try to change the default password using the curl command as
> follows,
>
> curl --user solr-admin:SolrRocks
> http://localhost:8983/solr/admin/authentication -H
> 'Content-type:application/json' -d '{"set-user":{"solr-admin":"s2019"}}'
>
>
>
> I get the following error message,
>
>
> 
>
> 
>
> 
>
> Error 403 Unauthorized request, Response code: 403
>
> 
>
> HTTP ERROR 403
>
> Problem accessing /solr/admin/authentication. Reason:
>
> Unauthorized request, Response code: 403
>
> 
>
> 
>
>
> Please help.
>
>
> *Thanks and Regards,*
> Salmaan Rashid Syed
> +91 8978353445 | www.panna.ai |
> 5550 Granite Pkwy, Suite #225, Plano TX-75024.
> Cyber Gateways, Hi-tech City, Hyderabad, Telangana, India.
>
>
>
> On Thu, Aug 1, 2019 at 1:48 PM Salmaan Rashid Syed <
> salmaan.ras...@mroads.com> wrote:
>
>> Hi Solr Users,
>>
>> I have enabled Solr basic authentication as shown in Solr documentations.
>>
>> I have changed username from solr to solr-admin as follow
>>
>> {
>> "authentication":{
>>"blockUnknown": true,
>>"class":"solr.BasicAuthPlugin",
>>
>>  "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
>> Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
>> },
>> "authorization":{
>>"class":"solr.RuleBasedAuthorizationPlugin",
>>"permissions":[{"name":"security-edit",
>>   "role":"admin"}],
>>"user-role":{"solr-admin":"admin"}
>> }}
>>
>> I am able to login to the page using the credentials
>> mroads-solr-admin:SolrRocks.
>>
>> But, when I try to change the default password using the curl command as
>> follows,
>>
>> curl --user mroads-solr-admin:SolrRocks
>> http://localhost:8983/solr/admin/authentication -H
>> 'Content-type:application/json' -d '{"set-user":{"mroads-solr":"Mroads@2019
>> #"}}'
>>
>>
>>
>> I get the following error message,
>>
>>
>> 
>>
>> 
>>
>> 
>>
>> Error 403 Unauthorized request, Response code: 403
>>
>> 
>>
>> HTTP ERROR 403
>>
>> Problem accessing /solr/admin/authentication. Reason:
>>
>> Unauthorized request, 

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Jan Høydahl]

Yes please do. I made the ZkStatus UI and it works by letting the solr node 
that Admin UI is connected to do 4LW commands to each ZK node and then 
concatenate the results. 

You could try to invoke each of the 4LW commands manually on each ZK server 
using telnet, and see if that succeeds for all hosts and commands..

telnet host.name 2181
conf

Jan Høydahl

> 1. aug. 2019 kl. 15:34 skrev Jörn Franke :
> 
> Spaces did not change the situation. In standalone it works without spaces 
> and the issue is only if there is an ensemble. I checked all ZK nodes have 
> the statement and have been restarted .
> 
> So issue pics there for a ZK Ensemble only in admin UI. I will create tonight 
> a JIRA if no one creates it before
> 
>> Am 01.08.2019 um 12:58 schrieb Erick Erickson :
>> 
>> The issue was only cosmetic in the sense that the admin UI was the only 
>> thing that was affected,
>> not other Solr functions when I was working on this.
>> 
>> Please check a few things:
>> 
>> 1> be absolutely sure that you’ve added this in all your zoo.cfg files
>> 
>> 2> the example on the ZooKeeper website has spaces, could you try that just 
>> to cover all bases? Stranger things have happened…
>> 
>> 4lw.commands.whitelist=mntr, ruok, conf
>> not
>> 4lw.commands.whitelist=mntr,ruok,conf
>> 
>> 3> if <1> and <2> don’t work, what happens if you start your ZooKeepers with 
>> -Dzookeeper.4lw.commands.whitelist=….
>> 
>> If it’s not <1> or <2>, please raise a JIRA.
>> 
>> Best,
>> Erick
>> 
>> Also, see: SOLR-13502 (no work has been done on this yet)
>> 
>>> On Aug 1, 2019, at 6:05 AM, Jörn Franke  wrote:
>>> 
>>> For me:
>>> * ZK stand-alone mode - no issues
>>> * ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI (I see 
>>> the same error message), but aside this Solr is working fine 
>>> 
>>> 
>>> 
 Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo :
 
 Hi Jörn,
 Thank you for your reply.
 
 I have encountered problem when I tried to create a collection with this
 new version of ZooKeeper. You can find my Solr log file here:
 https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
 
 Does it work perfectly at your side for creating collections and indexing
 even when running ZooKeeper ensemble?
 
 Regards,
 Edwin
 
 
> On Thu, 1 Aug 2019 at 17:39, Jörn Franke  wrote:
> 
> I confirm the issue.
> 
> Interestingly it does not happen with ZK standalone, but only in a ZK
> Ensemble.
> 
> It seems to be mainly cosmetic in the admin UI because Solr appears to
> function normally.
> 
>> Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo > :
>> 
>> Yes. You can get my full solr.log from the link below. The error is there
>> when I tried to create collection1 (around line 170 to 300) .
>> 
>> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
>> 
>> Regards,
>> Edwin
>> 
>> 
>>> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
> wrote:
>>> 
>>> Please look for the full log file solr.log in your Solr server, and
> share
>>> it via some file sharing service or gist or similar for us to be able to
>>> decipher the collection create error.
>>> 
>>> --
>>> Jan Høydahl, search solution architect
>>> Cominvent AS - www.cominvent.com
>>> 
 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
> edwinye...@gmail.com
 :
 
 Hi,
 
 Regarding the issue, I have tried to put the following in zoo.cfg under
 ZooKeeper:
 4lw.commands.whitelist=mntr,conf,ruok
 
 But it is still showing this error.
 *"Errors: - membership: Check 4lq.commands.whitelist setting in
> zookeeper
 configuration file."*
 
 As I am using SolrCloud, the collection config can still be loaded to
 ZooKeeper as per normal. But if I tried to create a collection, I will
>>> get
 the following error:
 
 {
 "responseHeader":{
 "status":400,
 "QTime":686},
 "failure":{
 "192.168.1.2:8983
>>> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
 occurred when talking to server at:http://192.168.1.2:8983/solr;,
 "192.168.1.2:8984
>>> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
 occurred when talking to server at:http://192.168.1.2:8984/solr"},
 "Operation create caused
 
>>> 
> exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
 Underlying core creation failed while creating collection:
> collection1",
 "exception":{f
 "msg":"Underlying core creation failed while creating collection:
 collection1",
 "rspCode":400},
 "error":{
 "metadata":[
 

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Jörn Franke]

Spaces did not change the situation. In standalone it works without spaces and 
the issue is only if there is an ensemble. I checked all ZK nodes have the 
statement and have been restarted .

So issue pics there for a ZK Ensemble only in admin UI. I will create tonight a 
JIRA if no one creates it before

> Am 01.08.2019 um 12:58 schrieb Erick Erickson :
> 
> The issue was only cosmetic in the sense that the admin UI was the only thing 
> that was affected,
> not other Solr functions when I was working on this.
> 
> Please check a few things:
> 
> 1> be absolutely sure that you’ve added this in all your zoo.cfg files
> 
> 2> the example on the ZooKeeper website has spaces, could you try that just 
> to cover all bases? Stranger things have happened…
> 
> 4lw.commands.whitelist=mntr, ruok, conf
> not
> 4lw.commands.whitelist=mntr,ruok,conf
> 
> 3> if <1> and <2> don’t work, what happens if you start your ZooKeepers with 
> -Dzookeeper.4lw.commands.whitelist=….
> 
> If it’s not <1> or <2>, please raise a JIRA.
> 
> Best,
> Erick
> 
> Also, see: SOLR-13502 (no work has been done on this yet)
> 
>> On Aug 1, 2019, at 6:05 AM, Jörn Franke  wrote:
>> 
>> For me:
>> * ZK stand-alone mode - no issues
>> * ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI (I see 
>> the same error message), but aside this Solr is working fine 
>> 
>> 
>> 
>>> Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo :
>>> 
>>> Hi Jörn,
>>> Thank you for your reply.
>>> 
>>> I have encountered problem when I tried to create a collection with this
>>> new version of ZooKeeper. You can find my Solr log file here:
>>> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
>>> 
>>> Does it work perfectly at your side for creating collections and indexing
>>> even when running ZooKeeper ensemble?
>>> 
>>> Regards,
>>> Edwin
>>> 
>>> 
 On Thu, 1 Aug 2019 at 17:39, Jörn Franke  wrote:
 
 I confirm the issue.
 
 Interestingly it does not happen with ZK standalone, but only in a ZK
 Ensemble.
 
 It seems to be mainly cosmetic in the admin UI because Solr appears to
 function normally.
 
> Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo  :
> 
> Yes. You can get my full solr.log from the link below. The error is there
> when I tried to create collection1 (around line 170 to 300) .
> 
> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> 
> Regards,
> Edwin
> 
> 
>> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
 wrote:
>> 
>> Please look for the full log file solr.log in your Solr server, and
 share
>> it via some file sharing service or gist or similar for us to be able to
>> decipher the collection create error.
>> 
>> --
>> Jan Høydahl, search solution architect
>> Cominvent AS - www.cominvent.com
>> 
>>> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
 edwinye...@gmail.com
>>> :
>>> 
>>> Hi,
>>> 
>>> Regarding the issue, I have tried to put the following in zoo.cfg under
>>> ZooKeeper:
>>> 4lw.commands.whitelist=mntr,conf,ruok
>>> 
>>> But it is still showing this error.
>>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
 zookeeper
>>> configuration file."*
>>> 
>>> As I am using SolrCloud, the collection config can still be loaded to
>>> ZooKeeper as per normal. But if I tried to create a collection, I will
>> get
>>> the following error:
>>> 
>>> {
>>> "responseHeader":{
>>> "status":400,
>>> "QTime":686},
>>> "failure":{
>>> "192.168.1.2:8983
>> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>>> occurred when talking to server at:http://192.168.1.2:8983/solr;,
>>> "192.168.1.2:8984
>> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>>> occurred when talking to server at:http://192.168.1.2:8984/solr"},
>>> "Operation create caused
>>> 
>> 
 exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
>>> Underlying core creation failed while creating collection:
 collection1",
>>> "exception":{f
>>> "msg":"Underlying core creation failed while creating collection:
>>> collection1",
>>> "rspCode":400},
>>> "error":{
>>> "metadata":[
>>>  "error-class","org.apache.solr.common.SolrException",
>>>  "root-error-class","org.apache.solr.common.SolrException"],
>>> "msg":"Underlying core creation failed while creating collection:
>>> collection1",
>>> "code":400}}
>>> 
>>> Is there anything which I may have missed out?
>>> 
>>> Regards,
>>> Edwin
>>> 
>>> On Tue, 30 Jul 2019 at 10:05, Zheng Lin Edwin Yeo <
 edwinye...@gmail.com>
>>> wrote:
>>> 
 Hi,
 
 I am using the new Solr 8.2.0 with SolrCloud and external ZooKeeper
>> 3.5.5.

SOLR 8.1.1 SynonymQuery(Synonym in parsedQuery

[Hodder, Rick]

 have a SOLR 4.10.2 core, and I am upgrading to 8.1.1.
When I compare parsedQuery for a search 4.10 vs 8.1.1 I am seeing the query 
wrapped with SynonymQuery(Synonym( in 8.1.1.
I think it may be because I replaced the deprecated SynonymFilterFactory with 
SynonymGraphFilterFactory.
Is this a new feature of the SynonymGraphFilterFactory? How can I remove that 
(or should I?)?
4.10.2
"querystring":"IDX_Company:blue",
"parsedquery":"(IDX_Company:b IDX_Company:bl IDX_Company:blu 
IDX_Company:blue)",
...
8.1.1
"querystring":"IDX_Company:blue",
"parsedquery":"SynonymQuery(Synonym(IDX_Company:b IDX_Company:bl 
IDX_Company:blu IDX_Company:blue))",
...
Here's the field def:



Here is the definition of text_general I am using in schema.xml

  

 







 
  
  

 







 
  

Re: Problem with uploading Large synonym files in cloud mode

[Salmaan Rashid Syed]

Thank you, I will definitely try it.

Regards,
Salmaan



On Thu, Aug 1, 2019 at 5:40 PM Bernd Fehling 
wrote:

>
>
> Am 01.08.19 um 13:57 schrieb Salmaan Rashid Syed:
> > After I make the -Djute.maxbuffer changes to Solr, deployed in
> production,
> > Do I need to restart the solr to be able to add synonyms >1MB?
>
> Yes, you have to restart Solr.
>
>
> >
> > Or, Was this supposed to be done before putting Solr to production ever?
> > Can we make chages when the Solr is running in production?
>
> It depends on your system. In my cloud with 5 shards and 3 replicas I can
> take one by one offline, stop, modify and start again without problems.
>
>
> >
> > Thanks.
> >
> > Regards,
> > Salmaan
> >
> >
> >
> > On Tue, Jul 30, 2019 at 4:53 PM Bernd Fehling <
> > bernd.fehl...@uni-bielefeld.de> wrote:
> >
> >> You have to increase the -Djute.maxbuffer for large configs.
> >>
> >> In Solr bin/solr/solr.in.sh use e.g.
> >> SOLR_OPTS="$SOLR_OPTS -Djute.maxbuffer=1000"
> >> This will increase maxbuffer for zookeeper on solr side to 10MB.
> >>
> >> In Zookeeper zookeeper/conf/zookeeper-env.sh
> >> SERVER_JVMFLAGS="$SERVER_JVMFLAGS -Djute.maxbuffer=1000"
> >>
> >> I have a >10MB Thesaurus and use 30MB for jute.maxbuffer, works perfect.
> >>
> >> Regards
> >>
> >>
> >> Am 30.07.19 um 13:09 schrieb Salmaan Rashid Syed:
> >>> Hi Solr Users,
> >>>
> >>> I have a very big synonym file (>5MB). I am unable to start Solr in
> cloud
> >>> mode as it throws an error message stating that the synonmys file is
> >>> too large. I figured out that the zookeeper doesn't take a file greater
> >>> than 1MB size.
> >>>
> >>> I tried to break down my synonyms file to smaller chunks less than 1MB
> >>> each. But, I am not sure about how to include all the filenames into
> the
> >>> Solr schema.
> >>>
> >>> Should it be seperated by commas like synonyms = "__1_synonyms.txt,
> >>> __2_synonyms.txt, __3synonyms.txt"
> >>>
> >>> Or is there a better way of doing that? Will the bigger file when
> broken
> >>> down to smaller chunks will be uploaded to zookeeper as well.
> >>>
> >>> Please help or please guide me to relevant documentation regarding
> this.
> >>>
> >>> Thank you.
> >>>
> >>> Regards.
> >>> Salmaan.
> >>>
> >>
> >
>

Re: Problem with uploading Large synonym files in cloud mode

[Bernd Fehling]

Am 01.08.19 um 13:57 schrieb Salmaan Rashid Syed:

After I make the -Djute.maxbuffer changes to Solr, deployed in production,
Do I need to restart the solr to be able to add synonyms >1MB?


Yes, you have to restart Solr.




Or, Was this supposed to be done before putting Solr to production ever?
Can we make chages when the Solr is running in production?


It depends on your system. In my cloud with 5 shards and 3 replicas I can
take one by one offline, stop, modify and start again without problems.




Thanks.

Regards,
Salmaan



On Tue, Jul 30, 2019 at 4:53 PM Bernd Fehling <
bernd.fehl...@uni-bielefeld.de> wrote:


You have to increase the -Djute.maxbuffer for large configs.

In Solr bin/solr/solr.in.sh use e.g.
SOLR_OPTS="$SOLR_OPTS -Djute.maxbuffer=1000"
This will increase maxbuffer for zookeeper on solr side to 10MB.

In Zookeeper zookeeper/conf/zookeeper-env.sh
SERVER_JVMFLAGS="$SERVER_JVMFLAGS -Djute.maxbuffer=1000"

I have a >10MB Thesaurus and use 30MB for jute.maxbuffer, works perfect.

Regards


Am 30.07.19 um 13:09 schrieb Salmaan Rashid Syed:

Hi Solr Users,

I have a very big synonym file (>5MB). I am unable to start Solr in cloud
mode as it throws an error message stating that the synonmys file is
too large. I figured out that the zookeeper doesn't take a file greater
than 1MB size.

I tried to break down my synonyms file to smaller chunks less than 1MB
each. But, I am not sure about how to include all the filenames into the
Solr schema.

Should it be seperated by commas like synonyms = "__1_synonyms.txt,
__2_synonyms.txt, __3synonyms.txt"

Or is there a better way of doing that? Will the bigger file when broken
down to smaller chunks will be uploaded to zookeeper as well.

Please help or please guide me to relevant documentation regarding this.

Thank you.

Regards.
Salmaan.

Re: Problem with uploading Large synonym files in cloud mode

[Salmaan Rashid Syed]

After I make the -Djute.maxbuffer changes to Solr, deployed in production,
Do I need to restart the solr to be able to add synonyms >1MB?

Or, Was this supposed to be done before putting Solr to production ever?
Can we make chages when the Solr is running in production?

Thanks.

Regards,
Salmaan



On Tue, Jul 30, 2019 at 4:53 PM Bernd Fehling <
bernd.fehl...@uni-bielefeld.de> wrote:

> You have to increase the -Djute.maxbuffer for large configs.
>
> In Solr bin/solr/solr.in.sh use e.g.
> SOLR_OPTS="$SOLR_OPTS -Djute.maxbuffer=1000"
> This will increase maxbuffer for zookeeper on solr side to 10MB.
>
> In Zookeeper zookeeper/conf/zookeeper-env.sh
> SERVER_JVMFLAGS="$SERVER_JVMFLAGS -Djute.maxbuffer=1000"
>
> I have a >10MB Thesaurus and use 30MB for jute.maxbuffer, works perfect.
>
> Regards
>
>
> Am 30.07.19 um 13:09 schrieb Salmaan Rashid Syed:
> > Hi Solr Users,
> >
> > I have a very big synonym file (>5MB). I am unable to start Solr in cloud
> > mode as it throws an error message stating that the synonmys file is
> > too large. I figured out that the zookeeper doesn't take a file greater
> > than 1MB size.
> >
> > I tried to break down my synonyms file to smaller chunks less than 1MB
> > each. But, I am not sure about how to include all the filenames into the
> > Solr schema.
> >
> > Should it be seperated by commas like synonyms = "__1_synonyms.txt,
> > __2_synonyms.txt, __3synonyms.txt"
> >
> > Or is there a better way of doing that? Will the bigger file when broken
> > down to smaller chunks will be uploaded to zookeeper as well.
> >
> > Please help or please guide me to relevant documentation regarding this.
> >
> > Thank you.
> >
> > Regards.
> > Salmaan.
> >
>

Re: Basic Authentication problem

[Salmaan Rashid Syed]

Hi Solr User,

Please help me with my issue.

I have enabled Solr basic authentication as shown in Solr documentations.

I have changed username from solr to solr-admin as follow

{
"authentication":{
   "blockUnknown": true,
   "class":"solr.BasicAuthPlugin",

 "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
},
"authorization":{
   "class":"solr.RuleBasedAuthorizationPlugin",
   "permissions":[{"name":"security-edit",
  "role":"admin"}],
   "user-role":{"solr-admin":"admin"}
}}

I am able to login to the page using the credentials solr-admin:SolrRocks.

But, when I try to change the default password using the curl command as
follows,

curl --user solr-admin:SolrRocks
http://localhost:8983/solr/admin/authentication -H
'Content-type:application/json' -d '{"set-user":{"solr-admin":"s2019"}}'


I get the following error message,








Error 403 Unauthorized request, Response code: 403



HTTP ERROR 403

Problem accessing /solr/admin/authentication. Reason:

Unauthorized request, Response code: 403






Please help.

Regards,
Salmaan


On Thu, Aug 1, 2019 at 1:51 PM Salmaan Rashid Syed <
salmaan.ras...@mroads.com> wrote:

> Small correction in the user-name. It is solr-admin everywhere.
>
> Hi Solr Users,
>
> I have enabled Solr basic authentication as shown in Solr documentations.
>
> I have changed username from solr to solr-admin as follow
>
> {
> "authentication":{
>"blockUnknown": true,
>"class":"solr.BasicAuthPlugin",
>
>  "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> },
> "authorization":{
>"class":"solr.RuleBasedAuthorizationPlugin",
>"permissions":[{"name":"security-edit",
>   "role":"admin"}],
>"user-role":{"solr-admin":"admin"}
> }}
>
> I am able to login to the page using the credentials
> mroads-solr-admin:SolrRocks.
>
> But, when I try to change the default password using the curl command as
> follows,
>
> curl --user solr-admin:SolrRocks
> http://localhost:8983/solr/admin/authentication -H
> 'Content-type:application/json' -d '{"set-user":{"solr-admin":"s2019"}}'
>
>
>
> I get the following error message,
>
>
> 
>
> 
>
> 
>
> Error 403 Unauthorized request, Response code: 403
>
> 
>
> HTTP ERROR 403
>
> Problem accessing /solr/admin/authentication. Reason:
>
> Unauthorized request, Response code: 403
>
> 
>
> 
>
>
> Please help.
>
>
> *Thanks and Regards,*
> Salmaan Rashid Syed
> +91 8978353445 | www.panna.ai |
> 5550 Granite Pkwy, Suite #225, Plano TX-75024.
> Cyber Gateways, Hi-tech City, Hyderabad, Telangana, India.
>
>
>
> On Thu, Aug 1, 2019 at 1:48 PM Salmaan Rashid Syed <
> salmaan.ras...@mroads.com> wrote:
>
>> Hi Solr Users,
>>
>> I have enabled Solr basic authentication as shown in Solr documentations.
>>
>> I have changed username from solr to solr-admin as follow
>>
>> {
>> "authentication":{
>>"blockUnknown": true,
>>"class":"solr.BasicAuthPlugin",
>>
>>  "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
>> Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
>> },
>> "authorization":{
>>"class":"solr.RuleBasedAuthorizationPlugin",
>>"permissions":[{"name":"security-edit",
>>   "role":"admin"}],
>>"user-role":{"solr-admin":"admin"}
>> }}
>>
>> I am able to login to the page using the credentials
>> mroads-solr-admin:SolrRocks.
>>
>> But, when I try to change the default password using the curl command as
>> follows,
>>
>> curl --user mroads-solr-admin:SolrRocks
>> http://localhost:8983/solr/admin/authentication -H
>> 'Content-type:application/json' -d '{"set-user":{"mroads-solr":"Mroads@2019
>> #"}}'
>>
>>
>>
>> I get the following error message,
>>
>>
>> 
>>
>> 
>>
>> 
>>
>> Error 403 Unauthorized request, Response code: 403
>>
>> 
>>
>> HTTP ERROR 403
>>
>> Problem accessing /solr/admin/authentication. Reason:
>>
>> Unauthorized request, Response code: 403
>>
>> 
>>
>> 
>>
>>
>> Please help.
>>
>>
>>
>> *Thanks and Regards,*
>> Salmaan Rashid Syed
>> +91 8978353445 | www.panna.ai |
>> 5550 Granite Pkwy, Suite #225, Plano TX-75024.
>> Cyber Gateways, Hi-tech City, Hyderabad, Telangana, India.
>>
>>
>

RE: SolrCloud recommended I/O RAID level

[Kaminski, Adi]

Hi Erick,

Thanks for the detailed explanation, much appreciated.



Regarding #1 reason you have mentioned - but if RAID10 is chosen per Shawn's 
suggestion, then we should be protected, no ? Unless you mean the whole server 
is not available
and not specific disk of configured RAID10.



Regarding #2 reason you have mentioned -

·   If we’re having 7 Solr node/servers as part of SolrCloud cluster, with 
48 vCPU in each server (so in total ~336 vCPU in total)

·   And we are talking about 2-3.2B of Solr docs distributed on this cluster

·   And assuming that each shard will handled 10M Solr docs in average 
(that what we saw is some forums as basic “rule of thumb”)

·   Questions:

o   Will additional replicas will assist with QPS ? As we will basically are 
having ratio of 1 vCPU per 1 shard (the mster replica)

o   Wouldn’t additional replicas will overclock per total amout of vCPUs, and 
actually cause delays in queries and lower QPS ?



Thanks,

Adi



-Original Message-
From: Erick Erickson 
Sent: Thursday, August 1, 2019 2:03 PM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud recommended I/O RAID level



“why would I need a replication factor of 2….”



Two reasons:



1> assuming your replicas are located on different physical machines, you can 
lose one and still keep on running. RAID won’t help if the machine dies.



2> capacity. Depending on your query load, having more than one replica 
distributes query loads across multiple Solr instances, increasing the QPS you 
can handle.



If you don’t care about either of those issues, then no reason.



Best,

Erick



> On Aug 1, 2019, at 2:11 AM, Kaminski, Adi 
> mailto:adi.kamin...@verint.com>> wrote:

>

> Hi Shawn,

> Thanks for your reply, fully agree with your comments, it clarifies more the 
> need of RAID10 in this case.

>

> One additional follow-up question - in case we follow this guidelines

> and having RAID10 (which leaves us with effective capacity of 50%),

> why would I need replication factor of 2 in our SolrCloud core/collection ? 
> Won't it be double protection layer, while the IO layer mirroring of RAID10 
> actually brings the value, and no need to copy anything when we have IO 
> failures ?

>

> Thanks,

> Adi

>

> -Original Message-

> From: Shawn Heisey mailto:apa...@elyograg.org>>

> Sent: Tuesday, July 30, 2019 9:44 PM

> To: solr-user@lucene.apache.org

> Subject: Re: SolrCloud recommended I/O RAID level

>

> On 7/30/2019 12:12 PM, Kaminski, Adi wrote:

>> Indeed RAID10 with both mirroring and striping should satisfy the

>> need, but per some benchmarks in the network there is still an impact

>> on write performance on it compared to RAID0 which is considered as

>> much better (attaching a table that summarizes different RAID levels

>> and their pros/cons and capacity ratio).

>

> RAID10 offers the best combination of performance and reliability.

> RAID0 might beat it *slightly* on performance, but if ANY drive fails on 
> RAID0, the entire volume is lost.

>

>> If we have ~200-320 shards spread by our 7 Solr node servers (part of

>> SolrCloud cluster) on single core/collection configured with

>> replication factor 2, shouldn't it supply applicative level

>> redundancy of indexed data ?

>

> Yes, you could rely on Solr alone for data redundancy.  But if there's a 
> drive failure, do you REALLY want to be single-stranded for the time it takes 
> to rebuild the entire server and copy data?  That's what you would end up 
> doing if you choose RAID0.

>

> It is true that RAID1 or RAID10 means you have to buy double your usable 
> capacity.  I would argue that drives are cheap and will cost less than either 
> downtime or sysadmin effort.

>

> Thanks,

> Shawn

>

>

> This electronic message may contain proprietary and confidential information 
> of Verint Systems Inc., its affiliates and/or subsidiaries. The information 
> is intended to be for the use of the individual(s) or entity(ies) named 
> above. If you are not the intended recipient (or authorized to receive this 
> e-mail for the intended recipient), you may not use, copy, disclose or 
> distribute to anyone this message or any information contained in this 
> message. If you have received this electronic message in error, please notify 
> us by replying to this e-mail.




This electronic message may contain proprietary and confidential information of 
Verint Systems Inc., its affiliates and/or subsidiaries. The information is 
intended to be for the use of the individual(s) or entity(ies) named above. If 
you are not the intended recipient (or authorized to receive this e-mail for 
the intended recipient), you may not use, copy, disclose or distribute to 
anyone this message or any information contained in this message. If you have 
received this electronic message in error, please notify us by replying to this 
e-mail.

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Erick Erickson]

Interestingly, the code that sets this system property also has spaces, as:

if (System.getProperty(ZK_WHITELIST_PROPERTY) == null) {
  System.setProperty(ZK_WHITELIST_PROPERTY, "ruok, mntr, conf");
}

Don’t know if that’s relevant or just a coincidence….

> On Aug 1, 2019, at 6:58 AM, Erick Erickson  wrote:
> 
> The issue was only cosmetic in the sense that the admin UI was the only thing 
> that was affected,
> not other Solr functions when I was working on this.
> 
> Please check a few things:
> 
> 1> be absolutely sure that you’ve added this in all your zoo.cfg files
> 
> 2> the example on the ZooKeeper website has spaces, could you try that just 
> to cover all bases? Stranger things have happened…
> 
> 4lw.commands.whitelist=mntr, ruok, conf
> not
> 4lw.commands.whitelist=mntr,ruok,conf
> 
> 3> if <1> and <2> don’t work, what happens if you start your ZooKeepers with 
> -Dzookeeper.4lw.commands.whitelist=….
> 
> If it’s not <1> or <2>, please raise a JIRA.
> 
> Best,
> Erick
> 
> Also, see: SOLR-13502 (no work has been done on this yet)
> 
>> On Aug 1, 2019, at 6:05 AM, Jörn Franke  wrote:
>> 
>> For me:
>> * ZK stand-alone mode - no issues
>> * ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI (I see 
>> the same error message), but aside this Solr is working fine 
>> 
>> 
>> 
>>> Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo :
>>> 
>>> Hi Jörn,
>>> Thank you for your reply.
>>> 
>>> I have encountered problem when I tried to create a collection with this
>>> new version of ZooKeeper. You can find my Solr log file here:
>>> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
>>> 
>>> Does it work perfectly at your side for creating collections and indexing
>>> even when running ZooKeeper ensemble?
>>> 
>>> Regards,
>>> Edwin
>>> 
>>> 
 On Thu, 1 Aug 2019 at 17:39, Jörn Franke  wrote:
 
 I confirm the issue.
 
 Interestingly it does not happen with ZK standalone, but only in a ZK
 Ensemble.
 
 It seems to be mainly cosmetic in the admin UI because Solr appears to
 function normally.
 
> Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo  :
> 
> Yes. You can get my full solr.log from the link below. The error is there
> when I tried to create collection1 (around line 170 to 300) .
> 
> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> 
> Regards,
> Edwin
> 
> 
>> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
 wrote:
>> 
>> Please look for the full log file solr.log in your Solr server, and
 share
>> it via some file sharing service or gist or similar for us to be able to
>> decipher the collection create error.
>> 
>> --
>> Jan Høydahl, search solution architect
>> Cominvent AS - www.cominvent.com
>> 
>>> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
 edwinye...@gmail.com
>>> :
>>> 
>>> Hi,
>>> 
>>> Regarding the issue, I have tried to put the following in zoo.cfg under
>>> ZooKeeper:
>>> 4lw.commands.whitelist=mntr,conf,ruok
>>> 
>>> But it is still showing this error.
>>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
 zookeeper
>>> configuration file."*
>>> 
>>> As I am using SolrCloud, the collection config can still be loaded to
>>> ZooKeeper as per normal. But if I tried to create a collection, I will
>> get
>>> the following error:
>>> 
>>> {
>>> "responseHeader":{
>>> "status":400,
>>> "QTime":686},
>>> "failure":{
>>> "192.168.1.2:8983
>> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>>> occurred when talking to server at:http://192.168.1.2:8983/solr;,
>>> "192.168.1.2:8984
>> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>>> occurred when talking to server at:http://192.168.1.2:8984/solr"},
>>> "Operation create caused
>>> 
>> 
 exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
>>> Underlying core creation failed while creating collection:
 collection1",
>>> "exception":{f
>>> "msg":"Underlying core creation failed while creating collection:
>>> collection1",
>>> "rspCode":400},
>>> "error":{
>>> "metadata":[
>>>  "error-class","org.apache.solr.common.SolrException",
>>>  "root-error-class","org.apache.solr.common.SolrException"],
>>> "msg":"Underlying core creation failed while creating collection:
>>> collection1",
>>> "code":400}}
>>> 
>>> Is there anything which I may have missed out?
>>> 
>>> Regards,
>>> Edwin
>>> 
>>> On Tue, 30 Jul 2019 at 10:05, Zheng Lin Edwin Yeo <
 edwinye...@gmail.com>
>>> wrote:
>>> 
 Hi,
 
 I am using the new Solr 8.2.0 with SolrCloud and external ZooKeeper
>> 3.5.5.
 
 However, after adding in the 

Re: Upgrading from 7.3 to 8.2

[Erick Erickson]

Please read the “Upgrade Notes” sections of CHANGES.txt for the versions 
between 7.3 and 8.2

It’s not necessary to upgrade ZooKeeper, but it is recommended if for no other 
reason than SSL isn’t supported on ZK 3.4.x

You should be able to upgrade directly to 8.2, _assuming_ your index was never, 
ever touched by Solr 6x, even in the distant past.

Best,
Erick

> On Aug 1, 2019, at 2:06 AM, Jayadevan Maymala  
> wrote:
> 
> Hi all,
> 
> We have a 3 node solr cluster - version 7.3.0 using zookeeper -version
> 3.4.12, running on CentOS Linux release 7.6.1810. I would like to upgrade
> to Solr version 8.2.
> Is it necessary to upgrade zookeeper also?
> Is it OK to upgrade directly to 8.2?
> Any tips/checklist would be welcome.
> 
> Regards,
> Jayadevan

Re: SolrCloud recommended I/O RAID level

[Erick Erickson]

“why would I need a replication factor of 2….”

Two reasons:

1> assuming your replicas are located on different physical machines, you can 
lose one and still keep on running. RAID won’t help if the machine dies.

2> capacity. Depending on your query load, having more than one replica 
distributes query loads across multiple Solr instances, increasing the QPS you 
can handle.

If you don’t care about either of those issues, then no reason.

Best,
Erick

> On Aug 1, 2019, at 2:11 AM, Kaminski, Adi  wrote:
> 
> Hi Shawn,
> Thanks for your reply, fully agree with your comments, it clarifies more the 
> need of RAID10 in this case.
> 
> One additional follow-up question - in case we follow this guidelines and 
> having RAID10 (which leaves us with effective capacity of 50%), why would I 
> need
> replication factor of 2 in our SolrCloud core/collection ? Won't it be double 
> protection layer, while the IO layer mirroring of RAID10 actually brings the 
> value, and no need to copy anything
> when we have IO failures ?
> 
> Thanks,
> Adi
> 
> -Original Message-
> From: Shawn Heisey 
> Sent: Tuesday, July 30, 2019 9:44 PM
> To: solr-user@lucene.apache.org
> Subject: Re: SolrCloud recommended I/O RAID level
> 
> On 7/30/2019 12:12 PM, Kaminski, Adi wrote:
>> Indeed RAID10 with both mirroring and striping should satisfy the
>> need, but per some benchmarks in the network there is still an impact
>> on write performance on it compared to RAID0 which is considered as
>> much better (attaching a table that summarizes different RAID levels
>> and their pros/cons and capacity ratio).
> 
> RAID10 offers the best combination of performance and reliability.
> RAID0 might beat it *slightly* on performance, but if ANY drive fails on 
> RAID0, the entire volume is lost.
> 
>> If we have ~200-320 shards spread by our 7 Solr node servers (part of
>> SolrCloud cluster) on single core/collection configured with
>> replication factor 2, shouldn't it supply applicative level redundancy
>> of indexed data ?
> 
> Yes, you could rely on Solr alone for data redundancy.  But if there's a 
> drive failure, do you REALLY want to be single-stranded for the time it takes 
> to rebuild the entire server and copy data?  That's what you would end up 
> doing if you choose RAID0.
> 
> It is true that RAID1 or RAID10 means you have to buy double your usable 
> capacity.  I would argue that drives are cheap and will cost less than either 
> downtime or sysadmin effort.
> 
> Thanks,
> Shawn
> 
> 
> This electronic message may contain proprietary and confidential information 
> of Verint Systems Inc., its affiliates and/or subsidiaries. The information 
> is intended to be for the use of the individual(s) or entity(ies) named 
> above. If you are not the intended recipient (or authorized to receive this 
> e-mail for the intended recipient), you may not use, copy, disclose or 
> distribute to anyone this message or any information contained in this 
> message. If you have received this electronic message in error, please notify 
> us by replying to this e-mail.

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Erick Erickson]

The issue was only cosmetic in the sense that the admin UI was the only thing 
that was affected,
not other Solr functions when I was working on this.

Please check a few things:

1> be absolutely sure that you’ve added this in all your zoo.cfg files

2> the example on the ZooKeeper website has spaces, could you try that just to 
cover all bases? Stranger things have happened…

4lw.commands.whitelist=mntr, ruok, conf
not
4lw.commands.whitelist=mntr,ruok,conf

3> if <1> and <2> don’t work, what happens if you start your ZooKeepers with 
-Dzookeeper.4lw.commands.whitelist=….

If it’s not <1> or <2>, please raise a JIRA.

Best,
Erick

Also, see: SOLR-13502 (no work has been done on this yet)

> On Aug 1, 2019, at 6:05 AM, Jörn Franke  wrote:
> 
> For me:
> * ZK stand-alone mode - no issues
> * ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI (I see 
> the same error message), but aside this Solr is working fine 
> 
> 
> 
>> Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo :
>> 
>> Hi Jörn,
>> Thank you for your reply.
>> 
>> I have encountered problem when I tried to create a collection with this
>> new version of ZooKeeper. You can find my Solr log file here:
>> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
>> 
>> Does it work perfectly at your side for creating collections and indexing
>> even when running ZooKeeper ensemble?
>> 
>> Regards,
>> Edwin
>> 
>> 
>>> On Thu, 1 Aug 2019 at 17:39, Jörn Franke  wrote:
>>> 
>>> I confirm the issue.
>>> 
>>> Interestingly it does not happen with ZK standalone, but only in a ZK
>>> Ensemble.
>>> 
>>> It seems to be mainly cosmetic in the admin UI because Solr appears to
>>> function normally.
>>> 
 Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo >>> :
 
 Yes. You can get my full solr.log from the link below. The error is there
 when I tried to create collection1 (around line 170 to 300) .
 
 https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
 
 Regards,
 Edwin
 
 
> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
>>> wrote:
> 
> Please look for the full log file solr.log in your Solr server, and
>>> share
> it via some file sharing service or gist or similar for us to be able to
> decipher the collection create error.
> 
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
> 
>> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
>>> edwinye...@gmail.com
>> :
>> 
>> Hi,
>> 
>> Regarding the issue, I have tried to put the following in zoo.cfg under
>> ZooKeeper:
>> 4lw.commands.whitelist=mntr,conf,ruok
>> 
>> But it is still showing this error.
>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
>>> zookeeper
>> configuration file."*
>> 
>> As I am using SolrCloud, the collection config can still be loaded to
>> ZooKeeper as per normal. But if I tried to create a collection, I will
> get
>> the following error:
>> 
>> {
>> "responseHeader":{
>> "status":400,
>> "QTime":686},
>> "failure":{
>> "192.168.1.2:8983
> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>> occurred when talking to server at:http://192.168.1.2:8983/solr;,
>> "192.168.1.2:8984
> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>> occurred when talking to server at:http://192.168.1.2:8984/solr"},
>> "Operation create caused
>> 
> 
>>> exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
>> Underlying core creation failed while creating collection:
>>> collection1",
>> "exception":{f
>> "msg":"Underlying core creation failed while creating collection:
>> collection1",
>> "rspCode":400},
>> "error":{
>> "metadata":[
>>   "error-class","org.apache.solr.common.SolrException",
>>   "root-error-class","org.apache.solr.common.SolrException"],
>> "msg":"Underlying core creation failed while creating collection:
>> collection1",
>> "code":400}}
>> 
>> Is there anything which I may have missed out?
>> 
>> Regards,
>> Edwin
>> 
>> On Tue, 30 Jul 2019 at 10:05, Zheng Lin Edwin Yeo <
>>> edwinye...@gmail.com>
>> wrote:
>> 
>>> Hi,
>>> 
>>> I am using the new Solr 8.2.0 with SolrCloud and external ZooKeeper
> 3.5.5.
>>> 
>>> However, after adding in the line under zoo.cfg
>>> *4lw.commands.whitelist=**
>>> 
>>> I get the error under Cloud -> ZK Status in Solr
>>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
> zookeeper
>>> configuration file."*
>>> 
>>> I have noticed that the issue is cause by adding the "conf" in the
>>> whitelist. But if I do not add the "conf" to the whitelist, I will get
> the
>>> following error:
>>> *"Errors: - conf is not executed 

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Jörn Franke]

For me:
* ZK stand-alone mode - no issues
* ZK Ensemble - it seems to be only a cosmetic issue in the Admin UI (I see the 
same error message), but aside this Solr is working fine 



> Am 01.08.2019 um 12:02 schrieb Zheng Lin Edwin Yeo :
> 
> Hi Jörn,
> Thank you for your reply.
> 
> I have encountered problem when I tried to create a collection with this
> new version of ZooKeeper. You can find my Solr log file here:
> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> 
> Does it work perfectly at your side for creating collections and indexing
> even when running ZooKeeper ensemble?
> 
> Regards,
> Edwin
> 
> 
>> On Thu, 1 Aug 2019 at 17:39, Jörn Franke  wrote:
>> 
>> I confirm the issue.
>> 
>> Interestingly it does not happen with ZK standalone, but only in a ZK
>> Ensemble.
>> 
>> It seems to be mainly cosmetic in the admin UI because Solr appears to
>> function normally.
>> 
>>> Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo >> :
>>> 
>>> Yes. You can get my full solr.log from the link below. The error is there
>>> when I tried to create collection1 (around line 170 to 300) .
>>> 
>>> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
>>> 
>>> Regards,
>>> Edwin
>>> 
>>> 
 On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
>> wrote:
 
 Please look for the full log file solr.log in your Solr server, and
>> share
 it via some file sharing service or gist or similar for us to be able to
 decipher the collection create error.
 
 --
 Jan Høydahl, search solution architect
 Cominvent AS - www.cominvent.com
 
> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
>> edwinye...@gmail.com
> :
> 
> Hi,
> 
> Regarding the issue, I have tried to put the following in zoo.cfg under
> ZooKeeper:
> 4lw.commands.whitelist=mntr,conf,ruok
> 
> But it is still showing this error.
> *"Errors: - membership: Check 4lq.commands.whitelist setting in
>> zookeeper
> configuration file."*
> 
> As I am using SolrCloud, the collection config can still be loaded to
> ZooKeeper as per normal. But if I tried to create a collection, I will
 get
> the following error:
> 
> {
> "responseHeader":{
>  "status":400,
>  "QTime":686},
> "failure":{
>  "192.168.1.2:8983
 _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
> occurred when talking to server at:http://192.168.1.2:8983/solr;,
>  "192.168.1.2:8984
 _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
> occurred when talking to server at:http://192.168.1.2:8984/solr"},
> "Operation create caused
> 
 
>> exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
> Underlying core creation failed while creating collection:
>> collection1",
> "exception":{f
>  "msg":"Underlying core creation failed while creating collection:
> collection1",
>  "rspCode":400},
> "error":{
>  "metadata":[
>"error-class","org.apache.solr.common.SolrException",
>"root-error-class","org.apache.solr.common.SolrException"],
>  "msg":"Underlying core creation failed while creating collection:
> collection1",
>  "code":400}}
> 
> Is there anything which I may have missed out?
> 
> Regards,
> Edwin
> 
> On Tue, 30 Jul 2019 at 10:05, Zheng Lin Edwin Yeo <
>> edwinye...@gmail.com>
> wrote:
> 
>> Hi,
>> 
>> I am using the new Solr 8.2.0 with SolrCloud and external ZooKeeper
 3.5.5.
>> 
>> However, after adding in the line under zoo.cfg
>> *4lw.commands.whitelist=**
>> 
>> I get the error under Cloud -> ZK Status in Solr
>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
 zookeeper
>> configuration file."*
>> 
>> I have noticed that the issue is cause by adding the "conf" in the
>> whitelist. But if I do not add the "conf" to the whitelist, I will get
 the
>> following error:
>> *"Errors: - conf is not executed because it is not in the whitelist.
 Check
>> 4lw.commands.whitelist setting in zookeeper configuration file."*
>> 
>> What could be the issue that cause this error, and how can we resolve
 it.
>> 
>> Thank you.
>> 
>> Regards,
>> Edwin
>> 
 
 
>> 

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Zheng Lin Edwin Yeo]

Hi Jörn,
Thank you for your reply.

I have encountered problem when I tried to create a collection with this
new version of ZooKeeper. You can find my Solr log file here:
https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN

Does it work perfectly at your side for creating collections and indexing
even when running ZooKeeper ensemble?

Regards,
Edwin


On Thu, 1 Aug 2019 at 17:39, Jörn Franke  wrote:

> I confirm the issue.
>
> Interestingly it does not happen with ZK standalone, but only in a ZK
> Ensemble.
>
> It seems to be mainly cosmetic in the admin UI because Solr appears to
> function normally.
>
> > Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo  >:
> >
> > Yes. You can get my full solr.log from the link below. The error is there
> > when I tried to create collection1 (around line 170 to 300) .
> >
> > https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> >
> > Regards,
> > Edwin
> >
> >
> >> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl 
> wrote:
> >>
> >> Please look for the full log file solr.log in your Solr server, and
> share
> >> it via some file sharing service or gist or similar for us to be able to
> >> decipher the collection create error.
> >>
> >> --
> >> Jan Høydahl, search solution architect
> >> Cominvent AS - www.cominvent.com
> >>
> >>> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo <
> edwinye...@gmail.com
> >>> :
> >>>
> >>> Hi,
> >>>
> >>> Regarding the issue, I have tried to put the following in zoo.cfg under
> >>> ZooKeeper:
> >>> 4lw.commands.whitelist=mntr,conf,ruok
> >>>
> >>> But it is still showing this error.
> >>> *"Errors: - membership: Check 4lq.commands.whitelist setting in
> zookeeper
> >>> configuration file."*
> >>>
> >>> As I am using SolrCloud, the collection config can still be loaded to
> >>> ZooKeeper as per normal. But if I tried to create a collection, I will
> >> get
> >>> the following error:
> >>>
> >>> {
> >>> "responseHeader":{
> >>>   "status":400,
> >>>   "QTime":686},
> >>> "failure":{
> >>>   "192.168.1.2:8983
> >> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
> >>> occurred when talking to server at:http://192.168.1.2:8983/solr;,
> >>>   "192.168.1.2:8984
> >> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
> >>> occurred when talking to server at:http://192.168.1.2:8984/solr"},
> >>> "Operation create caused
> >>>
> >>
> exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
> >>> Underlying core creation failed while creating collection:
> collection1",
> >>> "exception":{f
> >>>   "msg":"Underlying core creation failed while creating collection:
> >>> collection1",
> >>>   "rspCode":400},
> >>> "error":{
> >>>   "metadata":[
> >>> "error-class","org.apache.solr.common.SolrException",
> >>> "root-error-class","org.apache.solr.common.SolrException"],
> >>>   "msg":"Underlying core creation failed while creating collection:
> >>> collection1",
> >>>   "code":400}}
> >>>
> >>> Is there anything which I may have missed out?
> >>>
> >>> Regards,
> >>> Edwin
> >>>
> >>> On Tue, 30 Jul 2019 at 10:05, Zheng Lin Edwin Yeo <
> edwinye...@gmail.com>
> >>> wrote:
> >>>
>  Hi,
> 
>  I am using the new Solr 8.2.0 with SolrCloud and external ZooKeeper
> >> 3.5.5.
> 
>  However, after adding in the line under zoo.cfg
>  *4lw.commands.whitelist=**
> 
>  I get the error under Cloud -> ZK Status in Solr
>  *"Errors: - membership: Check 4lq.commands.whitelist setting in
> >> zookeeper
>  configuration file."*
> 
>  I have noticed that the issue is cause by adding the "conf" in the
>  whitelist. But if I do not add the "conf" to the whitelist, I will get
> >> the
>  following error:
>  *"Errors: - conf is not executed because it is not in the whitelist.
> >> Check
>  4lw.commands.whitelist setting in zookeeper configuration file."*
> 
>  What could be the issue that cause this error, and how can we resolve
> >> it.
> 
>  Thank you.
> 
>  Regards,
>  Edwin
> 
> >>
> >>
>

Re: Solr 8.2.0 having issue with ZooKeeper 3.5.5

[Jörn Franke]

I confirm the issue.

Interestingly it does not happen with ZK standalone, but only in a ZK Ensemble. 

It seems to be mainly cosmetic in the admin UI because Solr appears to function 
normally.

> Am 01.08.2019 um 03:31 schrieb Zheng Lin Edwin Yeo :
> 
> Yes. You can get my full solr.log from the link below. The error is there
> when I tried to create collection1 (around line 170 to 300) .
> 
> https://drive.google.com/open?id=1qkMLTRJ4eDSFwbqr15wSqjbg4dJV-bGN
> 
> Regards,
> Edwin
> 
> 
>> On Wed, 31 Jul 2019 at 18:39, Jan Høydahl  wrote:
>> 
>> Please look for the full log file solr.log in your Solr server, and share
>> it via some file sharing service or gist or similar for us to be able to
>> decipher the collection create error.
>> 
>> --
>> Jan Høydahl, search solution architect
>> Cominvent AS - www.cominvent.com
>> 
>>> 31. jul. 2019 kl. 08:33 skrev Zheng Lin Edwin Yeo >> :
>>> 
>>> Hi,
>>> 
>>> Regarding the issue, I have tried to put the following in zoo.cfg under
>>> ZooKeeper:
>>> 4lw.commands.whitelist=mntr,conf,ruok
>>> 
>>> But it is still showing this error.
>>> *"Errors: - membership: Check 4lq.commands.whitelist setting in zookeeper
>>> configuration file."*
>>> 
>>> As I am using SolrCloud, the collection config can still be loaded to
>>> ZooKeeper as per normal. But if I tried to create a collection, I will
>> get
>>> the following error:
>>> 
>>> {
>>> "responseHeader":{
>>>   "status":400,
>>>   "QTime":686},
>>> "failure":{
>>>   "192.168.1.2:8983
>> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>>> occurred when talking to server at:http://192.168.1.2:8983/solr;,
>>>   "192.168.1.2:8984
>> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
>>> occurred when talking to server at:http://192.168.1.2:8984/solr"},
>>> "Operation create caused
>>> 
>> exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
>>> Underlying core creation failed while creating collection: collection1",
>>> "exception":{f
>>>   "msg":"Underlying core creation failed while creating collection:
>>> collection1",
>>>   "rspCode":400},
>>> "error":{
>>>   "metadata":[
>>> "error-class","org.apache.solr.common.SolrException",
>>> "root-error-class","org.apache.solr.common.SolrException"],
>>>   "msg":"Underlying core creation failed while creating collection:
>>> collection1",
>>>   "code":400}}
>>> 
>>> Is there anything which I may have missed out?
>>> 
>>> Regards,
>>> Edwin
>>> 
>>> On Tue, 30 Jul 2019 at 10:05, Zheng Lin Edwin Yeo 
>>> wrote:
>>> 
 Hi,
 
 I am using the new Solr 8.2.0 with SolrCloud and external ZooKeeper
>> 3.5.5.
 
 However, after adding in the line under zoo.cfg
 *4lw.commands.whitelist=**
 
 I get the error under Cloud -> ZK Status in Solr
 *"Errors: - membership: Check 4lq.commands.whitelist setting in
>> zookeeper
 configuration file."*
 
 I have noticed that the issue is cause by adding the "conf" in the
 whitelist. But if I do not add the "conf" to the whitelist, I will get
>> the
 following error:
 *"Errors: - conf is not executed because it is not in the whitelist.
>> Check
 4lw.commands.whitelist setting in zookeeper configuration file."*
 
 What could be the issue that cause this error, and how can we resolve
>> it.
 
 Thank you.
 
 Regards,
 Edwin
 
>> 
>> 

Re: Mismatch between replication API & index.properties

[Atita Arora]

I am not sure but just guessing is this node acting as a repeater?

This seems legitimate as Jai mentioned above, the discrepancy could be
because of unsuccessful replication due to disk space constraints.


On Thu, Aug 1, 2019 at 6:19 AM Aman Tandon  wrote:

> Yes, that is what my understanding is but if you see the Replication
> handler response it is saying it is referring to the index folder not to
> the one shown in index.properties. Due to that confusion I am not able to
> delete the folder.
>
> Is this some bug or default behavior where irrespective of the
> index.properties it will always shows the index folder only.
>
> Solr version - 6.6.2
>
> On Wed, Jul 31, 2019, 21:17 jai dutt  wrote:
>
> > It's correct behaviour , Solr put replica index file in this format only
> > and you can find latest index pointing in index.properties file. Usually
> > afer successful full replication Solr remove old timestamp dir.
> >
> > On Wed, 31 Jul, 2019, 8:02 PM Aman Tandon, 
> > wrote:
> >
> > > Hi,
> > >
> > > We are having a situation where whole disk space is full and in server
> > > where we are seeing the multiple index directories ending with the
> > > timestamp. Upon checking the index.properties file for a particular
> shard
> > > replica, it is not referring to the folder name *index *but when I am
> > using
> > > the replication API I am seeing it is pointing to *index *folder. Am I
> > > missing something? Kindly advise.
> > >
> > > *directory*
> > >
> > >
> > >
> > > *drwxrwxr-x. 2 fusion fusion 69632 Jul 30 23:24 indexdrwxrwxr-x. 2
> fusion
> > > fusion 28672 Jul 31 03:02 index.20190731005047763drwxrwxr-x. 2 fusion
> > > fusion  4096 Jul 31 10:20 index.20190731095757917*
> > > -rw-rw-r--. 1 fusion fusion78  Jul 31 03:02 index.properties
> > > -rw-rw-r--. 1 fusion fusion   296 Jul 31 09:56
> replication.properties
> > > drwxrwxr-x. 2 fusion fusion  4096 Jan 16  2019 snapshot_metadata
> > > drwxrwxr-x. 2 fusion fusion  4096 Jul 30 23:24 tlog
> > >
> > > *index.properties*
> > >
> > > #index.properties
> > > #Wed Jul 31 03:02:12 EDT 2019
> > > index=index.20190731005047763
> > >
> > > *REPLICATION API STATUS*
> > >
> > > 
> > > 280.56 GB
> > > 
> > > */opt/solr/x_shard4_replica3/data/index/*
> > > 
> > > ...
> > > true
> > > false
> > > 1564543395563
> > > 98884
> > > ...
> > > ...
> > >
> > > Regards,
> > > Aman
> > >
> >
>

Re: Basic Authentication problem

[Salmaan Rashid Syed]

Small correction in the user-name. It is solr-admin everywhere.

Hi Solr Users,

I have enabled Solr basic authentication as shown in Solr documentations.

I have changed username from solr to solr-admin as follow

{
"authentication":{
   "blockUnknown": true,
   "class":"solr.BasicAuthPlugin",

 "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
},
"authorization":{
   "class":"solr.RuleBasedAuthorizationPlugin",
   "permissions":[{"name":"security-edit",
  "role":"admin"}],
   "user-role":{"solr-admin":"admin"}
}}

I am able to login to the page using the credentials
mroads-solr-admin:SolrRocks.

But, when I try to change the default password using the curl command as
follows,

curl --user solr-admin:SolrRocks
http://localhost:8983/solr/admin/authentication -H
'Content-type:application/json' -d '{"set-user":{"solr-admin":"s2019"}}'



I get the following error message,








Error 403 Unauthorized request, Response code: 403



HTTP ERROR 403

Problem accessing /solr/admin/authentication. Reason:

Unauthorized request, Response code: 403






Please help.


*Thanks and Regards,*
Salmaan Rashid Syed
+91 8978353445 | www.panna.ai |
5550 Granite Pkwy, Suite #225, Plano TX-75024.
Cyber Gateways, Hi-tech City, Hyderabad, Telangana, India.



On Thu, Aug 1, 2019 at 1:48 PM Salmaan Rashid Syed <
salmaan.ras...@mroads.com> wrote:

> Hi Solr Users,
>
> I have enabled Solr basic authentication as shown in Solr documentations.
>
> I have changed username from solr to solr-admin as follow
>
> {
> "authentication":{
>"blockUnknown": true,
>"class":"solr.BasicAuthPlugin",
>
>  "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
> Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
> },
> "authorization":{
>"class":"solr.RuleBasedAuthorizationPlugin",
>"permissions":[{"name":"security-edit",
>   "role":"admin"}],
>"user-role":{"solr-admin":"admin"}
> }}
>
> I am able to login to the page using the credentials
> mroads-solr-admin:SolrRocks.
>
> But, when I try to change the default password using the curl command as
> follows,
>
> curl --user mroads-solr-admin:SolrRocks
> http://localhost:8983/solr/admin/authentication -H
> 'Content-type:application/json' -d '{"set-user":{"mroads-solr":"Mroads@2019
> #"}}'
>
>
>
> I get the following error message,
>
>
> 
>
> 
>
> 
>
> Error 403 Unauthorized request, Response code: 403
>
> 
>
> HTTP ERROR 403
>
> Problem accessing /solr/admin/authentication. Reason:
>
> Unauthorized request, Response code: 403
>
> 
>
> 
>
>
> Please help.
>
>
>
> *Thanks and Regards,*
> Salmaan Rashid Syed
> +91 8978353445 | www.panna.ai |
> 5550 Granite Pkwy, Suite #225, Plano TX-75024.
> Cyber Gateways, Hi-tech City, Hyderabad, Telangana, India.
>
>

Basic Authentication problem

[Salmaan Rashid Syed]

Hi Solr Users,

I have enabled Solr basic authentication as shown in Solr documentations.

I have changed username from solr to solr-admin as follow

{
"authentication":{
   "blockUnknown": true,
   "class":"solr.BasicAuthPlugin",

 "credentials":{"solr-admin":"IV0EHq1OnNrj6gvRCwvFwTrZ1+z1oBbnQdiVC3otuq0=
Ndd7LKvVBAaZIF0QAVi1ekCfAJXr1GGfLtRUXhgrF8c="}
},
"authorization":{
   "class":"solr.RuleBasedAuthorizationPlugin",
   "permissions":[{"name":"security-edit",
  "role":"admin"}],
   "user-role":{"solr-admin":"admin"}
}}

I am able to login to the page using the credentials
mroads-solr-admin:SolrRocks.

But, when I try to change the default password using the curl command as
follows,

curl --user mroads-solr-admin:SolrRocks
http://localhost:8983/solr/admin/authentication -H
'Content-type:application/json' -d '{"set-user":{"mroads-solr":"Mroads@2019
#"}}'



I get the following error message,








Error 403 Unauthorized request, Response code: 403



HTTP ERROR 403

Problem accessing /solr/admin/authentication. Reason:

Unauthorized request, Response code: 403






Please help.



*Thanks and Regards,*
Salmaan Rashid Syed
+91 8978353445 | www.panna.ai |
5550 Granite Pkwy, Suite #225, Plano TX-75024.
Cyber Gateways, Hi-tech City, Hyderabad, Telangana, India.

RE: SolrCloud recommended I/O RAID level

[Kaminski, Adi]

Hi Shawn,
Thanks for your reply, fully agree with your comments, it clarifies more the 
need of RAID10 in this case.

One additional follow-up question - in case we follow this guidelines and 
having RAID10 (which leaves us with effective capacity of 50%), why would I need
replication factor of 2 in our SolrCloud core/collection ? Won't it be double 
protection layer, while the IO layer mirroring of RAID10 actually brings the 
value, and no need to copy anything
when we have IO failures ?

Thanks,
Adi

-Original Message-
From: Shawn Heisey 
Sent: Tuesday, July 30, 2019 9:44 PM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud recommended I/O RAID level

On 7/30/2019 12:12 PM, Kaminski, Adi wrote:
> Indeed RAID10 with both mirroring and striping should satisfy the
> need, but per some benchmarks in the network there is still an impact
> on write performance on it compared to RAID0 which is considered as
> much better (attaching a table that summarizes different RAID levels
> and their pros/cons and capacity ratio).

RAID10 offers the best combination of performance and reliability.
RAID0 might beat it *slightly* on performance, but if ANY drive fails on RAID0, 
the entire volume is lost.

> If we have ~200-320 shards spread by our 7 Solr node servers (part of
> SolrCloud cluster) on single core/collection configured with
> replication factor 2, shouldn't it supply applicative level redundancy
> of indexed data ?

Yes, you could rely on Solr alone for data redundancy.  But if there's a drive 
failure, do you REALLY want to be single-stranded for the time it takes to 
rebuild the entire server and copy data?  That's what you would end up doing if 
you choose RAID0.

It is true that RAID1 or RAID10 means you have to buy double your usable 
capacity.  I would argue that drives are cheap and will cost less than either 
downtime or sysadmin effort.

Thanks,
Shawn


This electronic message may contain proprietary and confidential information of 
Verint Systems Inc., its affiliates and/or subsidiaries. The information is 
intended to be for the use of the individual(s) or entity(ies) named above. If 
you are not the intended recipient (or authorized to receive this e-mail for 
the intended recipient), you may not use, copy, disclose or distribute to 
anyone this message or any information contained in this message. If you have 
received this electronic message in error, please notify us by replying to this 
e-mail.

Upgrading from 7.3 to 8.2

[Jayadevan Maymala]

Hi all,

We have a 3 node solr cluster - version 7.3.0 using zookeeper -version
3.4.12, running on CentOS Linux release 7.6.1810. I would like to upgrade
to Solr version 8.2.
Is it necessary to upgrade zookeeper also?
Is it OK to upgrade directly to 8.2?
Any tips/checklist would be welcome.

Regards,
Jayadevan