简体   繁体   中英

Gemfire - How to restrict/limit OQL queries for a region

Some users are executing OQL for regions that are triggering out of memory errors in a huge region. Sorting a query alone triggers an out of memory error.

Is there any configuration to weather restrict the memory footprint or forbid queries for a specific region?

As far as I know, there are not specific ways to restrict memory consumption only for queries.

There are, however, other options that you can use to make the cluster more resilient to these situations (aside from the obvious one: educate your users to not execute things like SELECT * on huge regions):

  1. Configure the Geode Resource Manager , which allows Geode to automatically cancel running queries whenever the memory is above a pre-configured threshold (see here ).
  2. Deploy a custom SecurityManager for authentication and authorization, and assign DATA:READ:RegionName permissions sparingly to your users. When security is enabled, users trying to execute OQL queries against a particular RegionName are required to have the DATA:READ:RegionName ResourcePermission assigned, so you can decide before hand to whom give this privileges. More details here .

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM