7:28 PM Thomas Corthals
wrote:
> Hi Reej,
>
> Have you tried with 2022-03-21T15:59:999Z (with a capital Z)?
>
> Regards,
>
> Thomas
>
> Op ma 21 mrt. 2022 om 12:20 schreef Reej Nayagam :
>
> > Hi All,
> >
> > In solr 4 , we had a date field and i
Hi All,
In solr 4 , we had a date field and in schema, fieldType name = date and
class ="solr.*TrieDateField*"
when moving to solr8, we changed the class to solr.*DatePointField*.
Now while filtering using solr4, the effective_date_dt : [* TO
2022-03-21T15:59:999z] works
but in solr8 the same th
, and now different stop ports are assigned to the 2 different nodes.
*Thanks,*
*Reej*
On Fri, Feb 18, 2022 at 9:26 AM Reej Nayagam wrote:
> Hi All,
> We have Solr cloud setup, version : 8.8.2
>
> I was able to set the stop port and everything was working fine.
>
> Initial se
and
did a fresh setup of the nodes
*Thanks,*
*Reej*
On Mon, Jan 10, 2022 at 3:36 PM Reej Nayagam wrote:
> Thanks Shawn, this worked.
> Thank you for the explanation & the help.
>
>
> *Thanks & Regards*
> *Reej*
>
>
> On Mon, Jan 10, 2022 at 7:45 AM Shawn Heis
,*
*Reej*
On Mon, Jan 10, 2022 at 3:36 PM Reej Nayagam wrote:
> Thanks Shawn, this worked.
> Thank you for the explanation & the help.
>
>
> *Thanks & Regards*
> *Reej*
>
>
> On Mon, Jan 10, 2022 at 7:45 AM Shawn Heisey wrote:
>
>> On 1/7/2022 4:55 A
Hi All,
Need your help in this.
The physical memory being used up in servers where solr nodes and zk are
installed .
At times the free space goes to 0 MB and slowly frees up some 100 MB
Using the windows resource monitor when we monitor, if we bring down zk
alone more than 40% of memory is relea
Hi,
But I remember there is a mention that it's not recommended to close the
solrclient.
We too have the same problem. The physical memory goes up to 20 GB and the
application server which makes calls to solr also slows down with hogging
threads. This issue is not until we upgraded from solr 4.1
s, is
this normal? what is the zk_node_count
ZK_node_count 1852
zk_approximate_data_size 7853679
*Thanks,*
*Reej*
On Thu, Jan 27, 2022 at 4:22 PM Reej Nayagam wrote:
> Hi Vinay,
>
> We are connecting using cloudsolrclient passing the zk host, so if zk is
> down, the connection to solr
he.org/doc/r3.4.8/zookeeperAdmin.html#sc_zkCommands
> >
> > This is how it works from a command line.
> >
> > $ echo ruok | nc zoo-shared-1.test.search.cheggnet.com 2181
> > imok
> >
> > wunder
> > Walter Underwood
> > wun...@wunderwood.org
> &
Thank you Shawn, I will try this way and see if it helps.
*Thanks,*
*Reej*
On Wed, Jan 26, 2022 at 10:59 PM Shawn Heisey wrote:
> On 1/26/22 06:53, Reej Nayagam wrote:
> > The scenario is solr servers are up, but majority of the zk is down,
> > so we need to tell the is
7;
>
> On Wed, Jan 26, 2022 at 8:54 AM Reej Nayagam wrote:
> >
> > The scenario is solr servers are up, but majority of the zk is down,
> > so we need to tell the issue is with the zookeeper. I don’t find a way on
> > how to identify the zookeeper status without wai
and? It's somewhere near there if not in CLUSTERSTATUS.
>
> For interacting with zookeeper itself I would probably just use zk
> clients directly.
>
>
>
> On Wed, Jan 26, 2022 at 7:41 AM Reej Nayagam wrote:
> >
> > Hi All,
> >
> > I need to ha
Hi All,
I need to handle zk failure and so monitoring the zk ensemble, and if the
majority of the zk fails we'll activate the HA to point to a DB search.
So to check if each of the zk is alive , we are connecting as below,
*zkClient = solrZkClient(zkaddress,1),*
*return zkclient.getSolrZooke
r can't be guaranteed to be partition tolerant anymore in
> all cases.
>
> Having said that, if you still want zookeeper to work properly even if 2
> nodes are down (somewhat unlike in most cases), then increase your
> zookeeper cluster to have 5 nodes.
>
> Thanks,
> Vina
Hi All,
We are using solr 8.82 cloud setup with zk ensemble 3.6.3 (3 zk servers).
We have a HA monitoring system which will ping every 5 mins to check if the
solr URL or shards are available and ping is success. If there is a failure
( if solr servers are down) it=E2=80=99ll flag to switch the sea
Thanks Shawn, this worked.
Thank you for the explanation & the help.
*Thanks & Regards*
*Reej*
On Mon, Jan 10, 2022 at 7:45 AM Shawn Heisey wrote:
> On 1/7/2022 4:55 AM, Reej Nayagam wrote:
> > I wonder how the existing port (8983) which is already being assigned to
> &g
Hi All,
If anyone can explain me the solr and jetty port details, why there is a
stop port for jetty and how to configure the stop ports as the stop port
has taken the port in which another solr server is listening.
Thanks
Reej
-- Forwarded message -
From: Reej Nayagam
Date: Fri
Adding few more info
Solr8 is https and solr4 is http.
Please advise on how to proceed.
Thanks
Reej
-- Forwarded message -
From: Reej Nayagam
Date: Fri, 7 Jan 2022 at 7:55 PM
Subject: Already listening port is assigned to dsolr.stop port
To: Solr
Hi All,
We have
Hi All,
We have configured solr8 cloud with ports 3983 and 9983 in server 1 and
server 2. So we have 2 solr servers 3 zookeepers running.
We have an existing solr4 version with ports 6983 and 8983 running in the
same server and different zk ports also.
Now the issue is we didn’t do any config ch
Hi All,
We have created a powershell script to run solr service in windows.
When running the service from the command line, the solr.log is created at
the configured path - SOLR_LOGS_DIR in solr.in.cmd file
But when starting as a service, even if there is a solr.log file, it gets
renamed to solr.
Thanks Shawn. Let me try to make my people understand. They want to make it
clear in the audit. Thanks for the information
Regards
Reej
On Thu, 30 Dec 2021 at 10:45 PM, Shawn Heisey wrote:
> On 12/30/2021 3:16 AM, Reej Nayagam wrote:
> > The Latest zookeeper release also uses log4j1.
Hi All,
The Latest zookeeper release also uses log4j1.x. Anyone has upgraded log4j
version to 2 for zookeeper.
We tried upgrading the log4j version, but the logs are not getting
generated.
If any of you have tried please let me know . Thank you
*Regards,*
*Reej*
Hi All,
We are having Zookeeper 3.6.3. Though log4j1.x is not vulnerable we are
advised to upgrade it to 2.17 in zookeeper.
We removed the log4j1.x and replaced it with log4j-1.2-api-2.17.0.jar,
log4j-api-2.17.0.jar and log4j-core-2.17.0.jar.
Now the issue is we cannot see the zookeeper logs writt
rraguntla
> wrote:
>
> >
> >- -Dlog4j2.formatMsgNoLookups=true
> >
> >
> > restart jvm with the above param and should work.
> >
> >
> >
> >
> >
> > On Saturday, December 11, 2021, 09:51:54 PM EST, Reej Nayagam <
> > reej...@
> wun...@wunderwood.org
> http://observer.wunderwood.org/ (my blog)
>
> > On Dec 11, 2021, at 8:28 PM, Reej Nayagam wrote:
> >
> > Thank you for your reply.
> >
> > It mentions Dlog4j2 but with solr4 it is log4j1.2.17
> > Can we use this command
above param and should work.
>
>
>
>
>
> On Saturday, December 11, 2021, 09:51:54 PM EST, Reej Nayagam <
> reej...@gmail.com> wrote:
>
> Hi All,
>
> In production we are using solr4 which uses log4j-1.2.17.jar.
>
> Can someone say the mitigation
Hi All,
In production we are using solr4 which uses log4j-1.2.17.jar.
Can someone say the mitigation option for solr4
Thanks
Reej
--
*Thanks,*
*Reej*
Hi All,
We are using Solr 8.8.2 cloud setup.
We have a monitoring app to monitor the solr indexing and alert if there is
a failure.
But the issue in SIT environment we have only around 10k to 15k documents
in each repository and the indexing status and responses are always
returned correctly,
In D
:
> On 11/29/21 11:40 PM, Reej Nayagam wrote:
> > We are using solr 8.8.2, upgraded oracle from 12c to 19c, so changed the
> > driver from ojdbc6.jar to ojdbc8_g.jar
> > Now while indexing, the logs shows the below. Sorry I cannot attach the
> log
> > file.
> >
&
Hi All,
We are using solr 8.8.2, upgraded oracle from 12c to 19c, so changed the
driver from ojdbc6.jar to ojdbc8_g.jar
Now while indexing, the logs shows the below. Sorry I cannot attach the log
file.
A month back this environment was working fine, connecting to oracle 12C,
and then the servers w
Hi Shawn,
Thanks a lot. Managed to stop the commits from client side and no more
errors now.
Appreciate your timely response. Thank you !
*Regards,*
*Reej*
On Wed, Aug 25, 2021 at 7:59 PM Shawn Heisey wrote:
> On 8/24/2021 10:08 PM, Reej Nayagam wrote:
> > Okay, Got your poin
On Wed, Aug 25, 2021 at 12:03 AM Shawn Heisey wrote:
> On 8/24/2021 1:51 AM, Reej M wrote:
> > So my doubt now is, Do we need to do any changes or wire anything for
> the optimisation and commit to be carried out effectively, as we are
> ignoring commit here or does solr internally will handle it
e let us know if any changes are required in the config.
Also, I could see the Error in solrwriter in the postimportdeletequery
"Exception while deleting query: "
So not sure if this has completely fixed or it'll reoccur again, confused.
*Thanks*
*Reej*
On 22 Aug 2021, at 7
Hi All,
We are getting a distributed update async exception during indexing. Solr
version v8.8.2 and we are using cloudsolrclient and passing 3 zk ip’s for
connecting. This indexing happens every 15 mins and at times the entire
indexing is getting wiped out with data being pulled from the DB.
Earl
her node fails, not sure why this
> is happening.
> Any advice is highly appreciated.
>
> *Thanks,*
> *Reej*
>
>
> On Tue, Aug 17, 2021 at 9:52 PM Shawn Heisey wrote:
>
>> On 8/16/2021 5:17 AM, Reej Nayagam wrote:
>> > Hi Shawn ,
>> &
Aug 17, 2021 at 9:52 PM Shawn Heisey wrote:
> On 8/16/2021 5:17 AM, Reej Nayagam wrote:
> > Hi Shawn ,
> > Please find the gc logs from our test server. Your help is much
> appreciated.
> >
> >
> https://drive.google.com/drive/folders/1VQqlRxiDnHWPUlmTUv83a8Cq
s.apache.org/jira/browse/SOLR-15587
>
> Will get this fixed in 8.10
>
> Cheers,
> Tim
>
> On Thu, Jul 22, 2021 at 6:23 PM Reej Nayagam wrote:
> >
> > Thanks Vincenzo D'Amore & Shawn
> > Hi Ours is a legacy system using EJB, no maven or graddle. And now
Hi Shawn ,
Please find the gc logs from our test server. Your help is much appreciated.
https://drive.google.com/drive/folders/1VQqlRxiDnHWPUlmTUv83a8CqCtvBP4le?usp=sharing
Also our Solr version is 8.8.2, so if there is a fix after 8.4+ , the 8.8.2
version should have this anyway right.
I've incr
> On 8 Aug 2021, at 11:05 AM, Reej Nayagam wrote:
>
> Hi All,
> We are getting this error during one of our scheduled indexing. Solr 8.8.2.
> We have configured the the dB connection in data-config.XML, dB is oracle.
>
> Error : JDBCDatasource was not closed prior to
Hi All,
We are getting this error during one of our scheduled indexing. Solr 8.8.2. We
have configured the the dB connection in data-config.XML, dB is oracle.
Error : JDBCDatasource was not closed prior to finalise(), indicates a bug -
POSSIBLE RESOURCE LEAK.
Kindly advise how to fix this.
Th
g is still correct for the
> current network setup.
> On Jul 29, 2021, 5:50 AM -0500, Reej Nayagam , wrote:
> > Hi All,
> >
> > Solr version - 8.8.2, Zookeeper - 3.6.3
> > we have 3 zk's configured and there were no changes.
> > All of a sudden, we got a er
> Hi All,
>
> Solr version - 8.8.2, Zookeeper - 3.6.3
>
> we have 3 zk's configured and there were no changes.
> All of a sudden, we got a error, too many connection from 192.xx.xx.
> maxconnection is 60.
>
> We stopped all the 3 zk's, cleared data and logs, and tried to restart, we
> get the bel
Hi All,
Solr version - 8.8.2, Zookeeper - 3.6.3
we have 3 zk's configured and there were no changes.
All of a sudden, we got a error, too many connection from 192.xx.xx.
maxconnection is 60.
We stopped all the 3 zk's, cleared data and logs, and tried to restart, we
get the below error
myid:1 war
zookeeper
> > > ensemble. Well, something like this:
> > >
> > >final List zkServers = new ArrayList();
> > >zkServers.add("zookeeper1:2181"); zkServers.add("zookeeper2:2181");
> > > zkServers.add("zookeeper3:2181");
> > >
Thanks Shawn In our application I saw noggit.jar added so after removing it
now I could instantiate with the zk IP’s. thanks for the help
On Thu, 22 Jul 2021 at 8:54 AM, Shawn Heisey wrote:
> On 7/21/2021 6:37 PM, Reej Nayagam wrote:
> > I tried earlier with zk ensemble, but when i t
l List zkServers = new ArrayList();
>zkServers.add("zookeeper1:2181"); zkServers.add("zookeeper2:2181");
> zkServers.add("zookeeper3:2181");
>final SolrClient client = new CloudSolrClient.Builder(zkServers,
> Optional.empty()).build();
>
>
>
Yes the passed url is with https
*Thanks,*
*Reej*
On Thu, Jul 22, 2021 at 3:40 AM Timothy Potter wrote:
> Does your `solrURL` value you're passing to `CloudSolrClient.Builder`
> start with `https`?
>
> On Wed, Jul 21, 2021 at 10:12 AM Reej Nayagam wrote:
> >
> >
-SolrCloud
> >>
> >> And double check the "clusterprop" urlScheme
> >>
> >> On Wed, Jul 21, 2021 at 11:01 AM Vincenzo D'Amore
> >> wrote:
> >>
> >>> Sorry for being so rude, I was in a hurry and just a while after the
>
Hi Sorry,
My offic system doesn't have internet for security reasons.
The issue is we have enabled ssl in solr and we try to get the clusterstate
as below
cloudsolrclient.getclusterstateprovider.getclusterstate()
then using the clusterstate doccollection
DocCollection dc = clusterstate.getCollect
On Thu, 8 Jul 2021 at 8:10 PM, sachin gk wrote:
> Have you upgraded the zookeeper too ? Sole 8.8.2 is compatible with
> zookeeper 3.5.5
>
zk version is 3.6.3
>
> On Thu, Jul 8, 2021, 17:35 Yuval Paz wrote:
>
> > What error do you see?
> >
> > Also, what are you trying to do? If you are trying t
Thanks a lot Shawn.
Regards
Reej
On Mon, 5 Jul 2021 at 1:27 PM, Shawn Heisey wrote:
> On 7/4/2021 8:55 PM, Reej Nayagam wrote:
> > Please find the versions as below
> > Solr core - 8.8.2
> > Solrj - 8.8.2
> > Zookeeper - 3.6.3
> > Zookeeper jute - 3.6.3
Hi Shawn,
Please find the versions as below
Solr core - 8.8.2
Solrj - 8.8.2
Zookeeper - 3.6.3
Zookeeper jute - 3.6.3
Kindly do share any code samples if you have them.
Thanks & Regards
Reej
On Fri, 2 Jul 2021 at 9:05 AM, Shawn Heisey wrote:
> On 7/1/2021 6:36 PM, Reej M wrote:
> > Hi Shawn /
ep the
> > monitoring
> > >> separate and to set different timeouts than for queries.
> > >>
> > >> This setup is simple and fast. With our biggest cluster, we index
> about
> > a
> > >> half million documents per minute.
> > >>
>
27;m used to reuse a CloudSolrClient instance for each
> collection/index.
>
> On Tue, Jun 29, 2021 at 3:12 PM Shawn Heisey wrote:
>
> > On 6/29/2021 6:43 AM, Reej Nayagam wrote:
> > > Hi Vincenzo Yes we are using cloud and initial solr version was 4.10.4
> > > and we upgr
n, why are you looking for the leader?
>
>> On Tue, Jun 29, 2021 at 1:58 PM Vincenzo D'Amore wrote:
>>
>> not sure I got your answer... are you using solrcloud?
>>
>>> On Tue, Jun 29, 2021 at 12:18 PM Reej Nayagam wrote:
>>>
>>> Hi
>&g
indly help
*Thanks,*
*Reej*
On Tue, Jun 29, 2021 at 6:17 PM Reej Nayagam wrote:
> Hi
> Thanks for the reply.
> I'm trying to create a singleton, but my worry is my base url changes
> based on the leader.
> so we have 14 repositories, and if we need to trigger indexing for 1
r speed.
>
> -Original Message-
> From: Reej Nayagam
> Sent: 29 June 2021 07:29
> To: Solr ; solr-user Lucene <
> solr-u...@lucene.apache.org>
> Subject: Fwd: HTTPSolrClient - help required
>
> Hi Team,
> Any advise is highly appreciated.
> Do we need
Hi Team,
Any advise is highly appreciated.
Do we need to use a singleton connection of a connection pool. Please kindly
advise
Thanks
Reej
Sent from my iPhone
Begin forwarded message:
> From: Reej Nayagam
> Date: 28 June 2021 at 11:53:58 AM SGT
> To: Solr , solr-user Lucene
>
Hi Team,
We recently upgraded to solr8.8.2
We have replaced all our httpsolrserver connections to httpsolrclient and
haven't explicitly closed the connections.
Even in solr4 we haven't closed the connections. But now our main
application has become too slow and it was said there is TIME_WAIT from t
> On 7 Jun 2021, at 11:58 AM, Shawn Heisey wrote:
>
> On 6/6/2021 8:35 AM, Reej Nayagam wrote:
>>> This was working in both cluster and standalone setups earlier in
>>> solr4.10.2 but in 8.8.2 was it not working. Kindly advise.
>>> This code is to fetch th
Hi Everyone,
We are using solr 8.8.2. We have set autoaddReplicas=false during collection
creation. We have a cluster setup with 2 servers and 4 nodes (2 nodes each).
When one node of a server is shutdown replicas are not replicated, when another
node of the server is also down, replicas were no
Hi Everyone,
> We are using solr 8.8.2. The solrjapi to fetch the clusterstate works fine
> with the clustersetup, but throws keeperexception, keeper error=session
> expired clusterstate.Jason or aliases.Json when trying in a standalone setup.
> Tried restarting the zk but not working.
> Code
Hi Everyone,
We are using solr 8.8.2. We have set autoaddReplicas=false during
collection creation. We have a cluster setup with 2 servers and 4 nodes (2
nodes each). When one node of a server is shutdown replicas are not
replicated, when another node of the server is also down, replicas were not
a
63 matches
Mail list logo