Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.1.2
-
Enterprise Edition 7.1.1 build 3166
-
Untriaged
-
Centos 64-bit
-
1
-
Unknown
Description
Came across this issue while testing honouring cgroup limits feature.
STEPS
Try to set eventing ram quota to a value greater than maximum allowed quota.
CASE A
Using api/v1/config REST API
curl -XPOST -k http://Administrator:password@172.23.106.67:8096/api/v1/config -d '{"ram_quota": 4000}' |
{
|
"restart": false |
}
|
Eventing ram quota updated successfully .
curl -XGET -k http://Administrator:password@172.23.106.67:8096/api/v1/config |
{
|
"enable_debugger": false, |
"ram_quota": 4000 |
}
|
2022-06-22T04:34:46.751-07:00 [Info] SuperSupervisor::GlobalConfigChangeCallback [1] Path => /eventing/settings/config value => { |
"enable_debugger": false, |
"ram_quota": 4000 |
}
|
2022-06-22T04:34:46.751-07:00 [Info] SuperSupervisor::HandleGlobalConfigChange [1] Config key: ram_quota value: 4000 |
2022-06-22T04:34:46.751-07:00 [Info] SuperSupervisor::updateQuotaForRunningFns [1] Notifying Eventing.Producer instances to update memory quota to 4000 MB |
2022-06-22T04:34:46.751-07:00 [Info] Producer::UpdateMemoryQuota [curl:1] Updating eventing memory quota to 4000 MB |
CASE B
Using pools/default endpoint or UI
Appropriate error displayed in this case.
curl -v -X POST -u Administrator:password \
|
http://172.23.106.67:8091/pools/default \ |
-d "eventingMemoryQuota=4000" |
{"errors":{"_":"Total quota (4000MB) exceeds the maximum allowed quota (3010MB) on node 'ns_1@172.23.106.67'"}} |
Attachments
Issue Links
- is a backport of
-
-
- Resolved
-