public void removeInChargeForConsume(String user, String operator) {
        InlongConsumePageRequest pageRequest = new InlongConsumePageRequest();
        pageRequest.setCurrentUser(user);
        pageRequest.setIsAdminRole(false);
        for (InlongConsumeEntity consumeEntity : consumeMapper.selectByCondition(pageRequest)) {
            if (Objects.equals(consumeEntity.getCreator(), user)) {
                consumeEntity.setCreator("admin");
            }
            Set<String> inChargeSet = Sets.newHashSet(consumeEntity.getInCharges().split(InlongConstants.COMMA));
            inChargeSet.remove(user);
            String updateInCharge = Joiner.on(",").join(inChargeSet);
            consumeEntity.setInCharges(updateInCharge);
            consumeEntity.setModifier(operator);
            int rowCount = consumeMapper.updateByIdSelective(consumeEntity);
            if (rowCount != InlongConstants.AFFECTED_ONE_ROW) {
                LOGGER.error("inlong consume has already updated, id={}, curVersion={}",
                        consumeEntity.getId(), consumeEntity.getVersion());
                throw new BusinessException(ErrorCodeEnum.CONFIG_EXPIRED);
            }
        }
    }
This implementation is just to intercept some error requests and reduce the pressure on the database.
<p/>
This is a memory-based implementation. There is a problem with concurrency security when there are
multiple service nodes because the data in memory cannot be shared.

@param req username login request
inlong-manager/manager-service/src/main/java/org/apache/inlong/manager/service/user/UserServiceImpl.java