System thread pool is used for cache and cache store operation. However, I would discourage you from limiting it to 1 thread.
In general, extend the cache store implementation you use and forward all CacheStore.read() operations to your single-threaded pool. -- Denis On Sun, Sep 9, 2018 at 11:41 AM Saikat Maitra <[email protected]> wrote: > Hi Mridul, > > Have you considered the option of creating a dedicated Threadpool for the > cache store operations. Here is an example > > http://commons.apache.org/dormant/threadpool/ > > Another option would be to consider Hystrix Command Threadpool since you > mentioned that the cache store is remote web service. > > https://github.com/Netflix/Hystrix/wiki/How-To-Use#Command%20Thread-Pool > > HTH > Regards > Saikat > > On Sun, Sep 9, 2018 at 6:04 AM, Mridul Chopra <[email protected]> > wrote: > >> Hello, >> >> I have implemented a cache store for read-through ignite caching, whenever >> there is a read-through operation through the cache-store, I want to limit >> this to single thread or at max 2. The reason behind the same is due to >> the >> fact that the underlying cache store is a remote Rest based webservice >> that >> can only support limited number of connections. Hence I want to have >> limited number of requests being sent for read-through. Please note that >> if >> I configure publicThreadPoolSize =1 , this would mean all cache.get and >> cache.getAll operations would be single threaded. Hence this behaviour is >> not desired, I want to have throttling at the cache store level only. >> Thanks, >> Mridul >> > >
