-
Quality Risk
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
NEW
-
NEW
-
---
-
---
KIE server update container API takes up all threads and blocks real time requests. In our application when we run update container API, some of our KIE containers are pretty big and it takes upto 2 seconds to 17 seconds to update KIE containers, during this time I have seen that it stops serving real time traffic and requests are piling up. how do we make sure our service is always up and running? Please let me know.
We run kie-server as a stand alone application.
does this one have anything do around org.kie.executor.pool.size? we have value as 30.
Our application serves around 1600 TPS traffic and that is 24 TPS per kubernetes pod.
this is our Kmodule:
<?xml version="1.0" encoding="UTF-8"?>
<kmodule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.drools.org/xsd/kmodule">
<kbase name="kbase" default="true" eventProcessingMode="stream" equalsBehavior="identity" packages="com.intuit.kie.personalization">
<ksession name="statelessKnowledgeSession" type="stateless" default="true" clockType="realtime"/>
</kbase>
</kmodule>