Question
Cts
IN
Last activity: 1 Sep 2016 8:43 EDT
Pega Rule Indexing issue
Hi,
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?
Hi,
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.
Thanks,
Bharath.
- 6 Views
***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.***
Pegasystems Inc.
IN
Hi Bharath,
Below PDN links should be helpful to resolve your issue.
https://collaborate.pega.com/question/search-not-working-unless-prefixed-old
Regards,
Supraja V
Pegasystems
IN
The following PDN links are useful
https://pdn.pega.com/community/pega-platform/question/database-bytes-input-exceeded-error-level (same error at a different place)
https://pdn.pega.com/understanding-pega0004-alert-quantity-data-received-database-query-exceeds-limit (config settings to change the values)
Cts
IN
Hi Rajiv,
Thanks for the reply and the links.
Hi Rajiv,
Thanks for the reply and the links.
Yes, i do understand that we can restrict the 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.
Please share your inputs.
Thanks,
Bharath.
Pegasystems
IN
Hi Bharath,
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.
-Rajiv
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.
Cts
IN
Hi Rajiv,
Thanks for the reply.
The issue is not with the size of the Rule.
The issue is with the size of the List that pega is preparing internally during the Rule indexing process.
Pega Log Error:
"Failed to index instance with key [RULE-OBJ-FLOW CSG-FW-IOPSFW-WORK-ITALY-COWO0788 COWO0788MAINFLOW #20150311T141222.758 GMT]
com.pega.pegarules.pub.PRRuntimeException:
The number of database bytes input for this interaction has exceeded the ERROR level for Requestor BDC18249186B94F0695A9131A8A70A365, operator Maximum bytes: 250000000 Actual bytes: 250891157:
code: <none> SQLState: <none> Message: <none> "
Now the flow Rule :COWO0788MAINFLOW is not indexed due to the above size issue(Size greater than 250 MB).
The size is not of the rule(The flow rule is a single step assignment with size less than 1 MB) rather the Rule stack/list that Pega assembled for rule indexing.
This is causing the issue and the application has no control over this.
Please share your inputs.
Thanks,
Bharath.