Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Sasidhar Bonigi (SasidharB9516)
Morgan Stanley
Principal Consultant
Morgan Stanley
US
SasidharB9516 Member since 2017 43 posts
Morgan Stanley
Posted: Oct 25, 2017
Last activity: Nov 30, 2018
Posted: 25 Oct 2017 11:58 EDT
Last activity: 30 Nov 2018 0:01 EST
Closed

Batch Indexing request failed. Possible cause: Quorum not met for writes to succeed. Action: Remove any offline nodes as index nodes

Please guides resolution for exception "Batch Indexing request failed. Possible cause: Quorum not met for writes to succeed. Action: Remove any offline nodes as index nodes"

To see attachments, please log in.
Data Integration

Posted: 7 years ago
Posted: 25 Oct 2017 12:19 EDT
Nick Loving (NickLoving_GCS)
PEGA
Senior Principal Engineer, Technical Support
Pegasystems Inc.
US

I believe this means that the number of index host nodes online doesn't meet the minimum requirement for elasticsearch.

You need to have at least ((total number of index host nodes) / 2) + 1 online for elasticsearch to work.

So if you have 6 nodes listed as indexing host nodes, at least 4 must be online ((6 / 2) + 1).

To see attachments, please log in.
Posted: 6 years ago
Posted: 24 Dec 2017 11:18 EST
Ravi Theja Solleti (RaviThejaS)
Valcon
Ravi Theja Solleti
Valcon
NL

We also have similar issues  in single node environment and the Node is online.

Indexing started working fine when we remove the node and add back. 

Any Idea, What could be possible reason for such error in Single Node Environment?

To see attachments, please log in.
Posted: 6 years ago
Posted: 24 Dec 2017 17:09 EST
Arun Kumar Mahanty (Arun_Mahanty)
Pegasystems Inc.
Principal Technical Solutions Engineer
Pegasystems Inc.
IN

Hello RaviTheja,

In search landing page the nodeid would have configured wrongly and that’s the reason after restart node id automatically picked up by the system and search started working .

So always check in case of single node the system node id is right .

Let me know if you have any other questions .

Thanks,

Arun

To see attachments, please log in.
Posted: 6 years ago
Posted: 27 Dec 2017 23:37 EST
Ravi Solleti (sollr1)
PEGA

Pegasystems Inc.

No, that was not the Case.
Below was the incident ,

Rule Index  and search was working fine but work search was not working which means Node ID is correct, when i check the status in landing page using check status of Each index, Rules was fine but work and Data are corrupted. I tried to reindex and got mentioned Error.All i did is remove the node and added it back with exact same details .After this reindexing is working fine.

So Node id is no the issues there should be some things else.

To see attachments, please log in.
Posted: 6 years ago
Posted: 31 Dec 2017 1:59 EST
Arun Kumar Mahanty (Arun_Mahanty)
Pegasystems Inc.
Principal Technical Solutions Engineer
Pegasystems Inc.
IN

Could you please share us the logs for the day you have faced the issue .

Are you seeing any hazelcast  related exception in the logs ?

Thanks, 

Arun

To see attachments, please log in.
Posted: 7 years ago
Posted: 2 Nov 2017 20:55 EDT
Sasidhar Bonigi (SasidharB9516)
Morgan Stanley
Principal Consultant
Morgan Stanley
US

Thank you Nick.

But does that mean its must to have multiple nodes?

We are running PRPC on single node and is enough for our scale. Also I see node as online

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice