Yossi, This is already supported in Geode. The resource manager functionality allows users to manage the resource, which takes care of blocking the cache operation under resource pressure. Also the subscription queue (if present); when full tries to throttle the cache op. Let me know if this is not what you are looking for.
http://geode.apache.org/docs/guide/18/managing/heap_use/heap_management.html -Anil. On Mon, Dec 17, 2018 at 1:33 AM Yossi Reginiano <[email protected]> wrote: > Hi team, > > > > Can u please insight us regarding what is the best approach to verify > whether we are in Throttling? Is there any solution for this in the geode > code? > > If there is no such approach – we thought about implementing the above in > our server applicative code – in which we will use a remote API function to > query each JVM for how many records it holds and once a certain Threshold > is reached we will assume that the JVM should not accept any new “put” > requests > > Please advise > > > > *Thanks,* > > *Yossi Reginiano* > > > > *This email and the information contained herein is proprietary and > confidential and subject to the Amdocs Email Terms of Service, which you > may review at* *https://www.amdocs.com/about/email-terms-of-service* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Dterms-2Dof-2Dservice&d=DwMFAg&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=V9fMlPdEaYR3cekeErxc41R665aUTnnNMJKtHPmf8nM&m=47a-ycfbskHVn12DalpVZ9ZgUOOExN7mGuchkHbrKp4&s=Ztrb-zSKCBAD2JshCNTxaxAhfaN0aHD8cWOQRfS7H1w&e=> >
