On Fri, Dec 15, 2017 at 3:56 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote:
> Hi Susankha, > > On Fri, Dec 15, 2017 at 3:26 PM, Susankha Nirmala <susan...@wso2.com> > wrote: > >> >> >> On Fri, Dec 15, 2017 at 3:14 PM, Pubudu Gunatilaka <pubu...@wso2.com> >> wrote: >> >>> Hi Susankha, >>> >>> We have a guide which explains when to use hazelcast clustering in [1]. >>> >>> If you don't have clustering enabled, the following are expected. >>> >>> 1. Immediate revocation of tokens among the gateways >>> >> >> How this happen when clustering disable? >> >> > > Sorry about the wording. I meant those will not work without clustering. > Let me rephrase this again. > > 1. Token revoke - You need to have clustering enabled. Otherwise, from > the other node gateway node you can access the API until cache timeout > happens. > Yes, this is a known behavior and for that reason I have initiated this mail thread. > 2. Backend service throttling - As we are not sharing throttling limits > within the gateway nodes, backend service throttling will not work. > > Thank you! > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Senior Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > -- Susankha Nirmala Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware Mobile : +94 77 593 2146 blog : https://susankhanirmala.wordpress.com/
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
