We have recently upgraded our application from Pega 5.5 to Pega 7.1.9.
And we tried using the Elastic search from then on.
When we tried running the Rule - Indexing . The Rule indexing is completed successfully after an Hour.
But when i see the Log files there are around 1880 rules couldn’t be indexed as they raised an error like the following:
2016-08-17 11:34:09,826 [fault (self-tuning)'] [ STANDARD] [ ] [IOPSSandbox:04.19.01] ( internal.es.AbstractIndexer) WARN F115082 - Failed to index instance with key [RULE-OBJ-WHEN CSG-FW-IOPSFW-WORK-COWO0771 ISVALIDPID #20160222T161942.839 GMT]
com.pega.pegarules.pub.PRRuntimeException: The number of database bytes input for this interaction has exceeded the ERROR level for Requestor B7E6A9E4DE13CCF40EE4D6212EE1AB54F, operator Maximum bytes: 250000000 Actual bytes: 250002827: code: <none> SQLState: <none> Message: <none>
In this case, it’s not possible to find named rule, it will only be possible to find it by using ‘old:’ syntax.
Does any one face this issue with there applications?
Any Article or Document would be helpful.
***Updated by Moderator: Marissa. Removed user added Ask the Expert group tag. Apologies for confusion, shouldn't have been an end-user option; updated category.***
Yes, i do understand that we can restrictthe size of data received on DB queries.
But my concern was why is this happening in the first place?
Since running the rule indexing is pega inbuilt feature. The rules it is fetching to index (the List and the Size) shouldn't it be controlled internally by Pega?
Increasing the interactionByteThreshold might be an option , but this has global impact and i need to revert back the setting after each indexing and Unfortunately in our environment we usually run the Rule indexing quite often.
I understand you concern but Pega platform does not have control over the size of rules the customer creates. Pega platform also gives the customer to define what is the interactionByteThreshold that they want to set for their environment (which some default provided by the platform). Given this, rule indexing cannot ignore the governance in place just because the feature is available out of the box in the platform.
I urge you to revisit your rules and see if you can indeed reduce the size. Otherwise, changing the config setting is the only way forward here.
P.S. Note that if we do ignore the settings, the performance impact could be drastic. While they may not manifest immediately, it may affect in future. Also, while this maybe a valid scenario for your application, the same may not hold true for all customers.