alibaba/nacos · error · NacosException
Configuration limit exceeded [group=%s, namespaceId=%s].
Error message
Configuration limit exceeded [group=%s, namespaceId=%s].
What it means
Error "Configuration limit exceeded [group=%s, namespaceId=%s]." thrown in alibaba/nacos.
Source
Thrown at config/src/main/java/com/alibaba/nacos/config/server/aspect/CapacityManagementAspect.java:153
* Write operation. Step 1: count whether to open the limitation checking function for capacity management; Step 2:
* open limitation checking capacity management and check size of content and quota;
*
* @throws Throwable Exception.
*/
private Object do4Insert(ProceedingJoinPoint pjp, String group, String namespaceId,
String content) throws Throwable {
LOGGER.info("[CapacityManagement] Handling insert operation for group: {}, namespaceId: {}",
group, namespaceId);
CounterMode counterMode = CounterMode.INCREMENT;
boolean hasTenant = StringUtils.isNotBlank(namespaceId);
if (PropertyUtil.isCapacityLimitCheck()) {
// Write or update: usage + 1
LimitType limitType = getLimitType(counterMode, group, namespaceId, content, hasTenant);
if (limitType != null) {
ErrorCode errorCode = ErrorCode.getErrorCode(limitType.name());
if (errorCode != null) {
throw new NacosException(errorCode.getCode(),
String.format("Configuration limit exceeded [group=%s, namespaceId=%s].",
group, namespaceId));
}
}
} else {
// Write or update: usage + 1
insertOrUpdateUsage(group, namespaceId, counterMode, hasTenant);
}
return getResult(pjp, group, namespaceId, counterMode, hasTenant);
}
/**
* Intercept delete config operations to perform capacity management checks.
*/
@Around(DELETE_CONFIG)
public Object aroundDeleteConfig(ProceedingJoinPoint pjp) throws Throwable {
if (!PropertyUtil.isManageCapacity()) {
return pjp.proceed();View on GitHub (pinned to 9b989acdf1)
Solutions
- Reduce the size or count of the input so it stays within the configured limit.
When it happens
Trigger: Thrown at config/src/main/java/com/alibaba/nacos/config/server/aspect/CapacityManagementAspect.java:153 when the library encounters an invalid state.
Common situations: Creating more configurations than the quota for the group/namespace allows.
AI-assisted analysis of alibaba/nacos@9b989acdf1 (2026-08-14).
Data as JSON: /api/errors/0a519ef0533e5b6d.
Report an issue: GitHub.