{"componentChunkName":"component---src-templates-acg-portal-new-template-tsx","path":"/zmq55eu6x","result":{"data":{"markdownRemark":{"html":"

一、快速入门

\n

1.1 前置条件

\n

已部署 Kubernetes 集群（CCE/自建K8s），并且完成RapidFS Cache Service组件安装（安装步骤详见章节二详细部署）

\n\n

已创建 RapidFS Master 托管实例（Cache接入类型： 容器引擎CCE、自有Kubernetes集群），并获得以下信息用于创建部署组：

\n\n

RapidFS Master托管实例必须和Kubernetes集群网络互通（如果网络不通，创建的部署组状态为PermissionDenied）

\n

RapidFS部署组负载（Pod）依赖7000～9000端口，对于公有云场景需要vpc安全组开放7000-9000

\n

1.2 部署组示例

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1apiVersion: rapidfs.baidu.com/v1alpha1\n2kind: RapidFSCacheDeploy\n3metadata:\n4  name: my-cache-deploy\n5  namespace: default\n6spec:\n7  # 部署组实际负载的副本数\n8  replicas: 3\n9  # rapidfs实例id\n10  rapidfsID: "your-rapidfs-id"\n11  # rapidfs实例token\n12  rapidfsToken: "your-token"\n13  storage:\n14  - mediumtype: MEM\n15    volumeType: emptyDir\n16    quota: "50Gi"
\n
\n
\n
\n \n

1.3 创建并验证

\n

Kubernetes集群侧检查

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1# 创建 部署组\n2kubectl apply -f my-cache-deploy.yaml\n3\n4# 查看状态\n5kubectl get rfscd\n6\n7# 查看详细信息\n8kubectl describe rfscd my-cache-deploy\n9\n10# 查看 Pod\n11kubectl get pods -o wide -l \"rapidfs.baidu.com/cachedeploy=my-cache-deploy\"
\n
\n
\n
\n \n

RapidFS Master托管实例侧验证

\n

请在百度公有云 数据湖存储加速工具 → 实例 → Cache 节点管理 查看部署组和节点信息

\n

二、详细部署

\n

2.1 前置依赖

\n

组件依赖Kruise，需要通过 Helm 模版安装Kruise组件（公有云CCE）

\n

\"image_1.png\"

\n

2.2 容器环境组件安装

\n

分CCE和自建K8s两种情况：

\n

2.2.1 CCE集群

\n
    \n
  1. 登录百度云容器引擎控制台
    2. \n
  2. 进入Helm → Helm 模版 → 百度智能云模版
    3. \n
  3. 检查安装参数中的region，必须和实际的地域对应
    4. \n
\n

\"image_1.png\"

\n
    \n
  1. 搜索 RapidFS Cache Service，点击安装，等待安装完成
    2. \n
  2. 查看 RapidFS缓存控制器Token：查看 kube-system namespace下的 ConfigMap rapidfs-cache-service-config 资源，获取data.rapidfsCacheControllerToken 属性值记为RapidFS缓存控制器Token，用于RapidFS实例与容器环境交互的身份识别；
    3. \n
\n

2.2.2 自建K8s集群

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1# 1. 安装，必须填入region参数，否则组件安装失败，如果是在B区安装，请询问rapidfs 同学确定region\n2# 1.1 获取EKS/自建K8S的服务地址: ${CLUSTER-IP} ${PORT}, EKS和自建K8S需要指定集群的实际服务地址\n3# NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE\n4# kubernetes   ClusterIP   10.96.0.1    <none>        443/TCP   2y22d\n5kubectl get service kubernetes\n6# 1.2 获取集群可用的调度器: ${SchedulerName}，EKS和自建K8S需要指定集群的实际的调度器\n7# 1.3 将values.yaml中的deployEnv设置为 eks\n8# 1.4 解压部署包，修改values.yaml文件的region、kubernetesServiceHost、kubernetesServicePort、schedulerName、manager.schedulerName 内容\n9helm install rapidfs-cache-service --namespace kube-system .\n10\n11# 2. 获取 RapidFS缓存控制器ID 和 RapidFS缓存控制器Token\n12# RapidFS缓存控制器ID: data.rapidfsCacheControllerID\n13# RapidFS缓存控制器Token: data.rapidfsCacheControllerToken\n14kubectl get configmap rapidfs-cache-service-config -n kube-system -o yaml
\n
\n
\n
\n \n

2.3 创建 RapidFS Master 托管实例

\n

按顺序进行控制台操作：数据湖存储加速工具 → 实例 → 创建实例\n选择部署模式：Master托管，根据Cache接入类型选择 容器引擎CCE 或者 自有Kubernetes集群

\n

\"image_1.png\"

\n

2.4 创建 部署组

\n

部署组配置

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1apiVersion: rapidfs.baidu.com/v1alpha1\n2kind: RapidFSCacheDeploy\n3metadata:\n4  name: cache-deploy-demo                 # 部署组名称\n5  namespace: default                      # 部署组所在命名空间\n6spec:\n7  rapidfsToken: "your-rapidfs-token"      # rapidfs master托管实例 实例Token\n8  rapidfsID: "rapidfs-xxxxxxxxxxxx"       # rapidfs master托管实例 实例ID\n9  replicas: 3                             # 部署组实际负载的副本数量\n10  region: "bj"                            # rapidfs master托管实例 所在地域\n11\n12  resources:                              # rapidfs部署组的资源设置，对rapidfs数据负载（pod）生效\n13    request:\n14      cpu: "2"\n15      memory: "4Gi"\n16    limits:\n17      cpu: "4"\n18      memory: "8Gi"\n19\n20  storage:                                # 提供给rapidfs部署组 数据负载的存储配置，注意，可以设置多个存储，但不能同时设置MEM 和 SSD 介质类型的 storage\n21    - mediumtype: MEM\n22      volumeType: emptyDir\n23      path: /data/rapidfs-cache\n24      quota: "4Gi"\n25    - mediumtype: SSD\n26      volumeType: hostPath\n27      path: /data/rapidfs-cache\n28      quota: "100Gi"\n29\n30  nodeSelector:                           # rapidfs部署组的nodeSelector，对rapidfs数据负载（pod）生效，"disktype: ssd"只是示例\n31    disktype: ssd\n32\n33  tolerations:                            # rapidfs部署组的tolerations，对rapidfs数据负载（pod）生效\n34    - key: "rapidfs"\n35      operator: "Equal"\n36      value: "cache"\n37      effect: "NoSchedule"\n38\n39  affinity:                               # rapidfs部署组的affinity，对rapidfs数据负载（pod）生效\n40    nodeAffinity:\n41      requiredDuringSchedulingIgnoredDuringExecution:\n42        nodeSelectorTerms:\n43        - matchExpressions:\n44          - key: node-type\n45            operator: In\n46            values: cache\n47          \n48  systemConfig:                           # 系统配置，除非用户有明确需求，否则不建议用户直接修改，修改前请和rapidfs同学确认\n49    - fs.aio-max-nr: "10485760"\n50    - vm.max_map_count: "655350"\n51\n52  serviceConfig:                          # 服务配置，不建议用户修改\n53    - min_log_level: "0"
\n
\n
\n
\n \n

三、部署组配置说明

\n

3.1 必填字段

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
字段类型说明示例
replicasintegerDataserver 副本数10
rapidfsIDstringRapidFS 实例 ID\"rapidfs-xHiwZKQ5q7jX\"
storagearray存储配置列表见下方说明
\n

3.2 存储配置（storage）

\n
\n

注意：对于一个部署组，不能同时设置MEM类型和SSD类型的storage，只能设置一种

\n
\n\n
\n
\n
\n YAML\n \n
\n
\n 
1storage:\n2  # MEM 存储（内存）\n3  - mediumtype: MEM           # 存储介质：MEM 或 SSD\n4    volumeType: emptyDir      # 卷类型：MEM 建议用 emptyDir\n5    quota: "50Gi"             # 存储配额\n6    \n7  # SSD 存储（固态硬盘）\n8  - mediumtype: SSD\n9    volumeType: hostPath      # 卷类型：SSD 建议用 hostPath\n10    path: /ssd-disk           # 挂载路径（hostPath 必填）\n11    quota: "500Gi"
\n
\n
\n
\n \n

3.3 资源配置（resources）

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1resources:\n2  request:                    # 最小资源请求\n3    memory: "1Gi"\n4    cpu: "1"\n5  limits:                     # 最大资源限制\n6    memory: "128Gi"\n7    cpu: "16"
\n
\n
\n
\n \n

推荐配置：

\n\n\n\n\n\n\n\n\n\n\n\n\n\n
memory (request/limit)cpu (request/limit)
20Gi / 128Gi4 / 16
\n
\n

未设置或低于最低要求时，Controller 会自动校准

\n
\n

3.4 调度配置

\n

3.4.1 节点选择器（nodeSelector）

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1nodeSelector:\n2  node-type: cache            # 只调度到带此标签的节点
\n
\n
\n
\n \n

3.4.2 亲和性（affinity）

\n
\n

部署组的实际负载配置了Pod之间的反亲和性，同一个部署组的Pod不会调度在同一个节点上

\n
\n\n
\n
\n
\n YAML\n \n
\n
\n 
1affinity:\n2  nodeAffinity:\n3    requiredDuringSchedulingIgnoredDuringExecution:\n4      nodeSelectorTerms:\n5      - matchExpressions:\n6        - key: node-type\n7          operator: In\n8          values: [cache]
\n
\n
\n
\n \n

3.4.3 污点容忍（tolerations）

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1tolerations:\n2- key: "dedicated"\n3  operator: "Equal"\n4  value: "rapidfs-cache"\n5  effect: "NoSchedule"
\n
\n
\n
\n \n

3.5 高级配置

\n
\n

除非有特殊要求，否则不建议用户通过systemConfig 和 serviceConfig修改配置

\n
\n

3.5.1 系统配置（systemConfig）

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1systemConfig:\n2- fs.aio-max-nr: "10485760"\n3- vm.max_map_count: "655350"
\n
\n
\n
\n \n

3.5.2 服务配置（serviceConfig）

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1serviceConfig:\n2- min_log_level: "0"\n3- comlog_quota_size: "1024"
\n
\n
\n
\n \n

四、状态查看

\n

4.1 部署组状态查看

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1# 查看所有 部署组 及状态\n2kubectl get rfscd\n3\n4# 示例输出\n5NAME                 PHASE     REPLICAS   READY   CLUSTER ADDRESS          AGE\n6my-cache-deploy      Ready     10         10      192.168.1.100:8000       1h\n7\n8# 查看详细信息\n9kubectl describe rfscd my-cache-deploy\n10\n11# 查看状态详情\n12kubectl get rfscd my-cache-deploy -o yaml\n13\n14# 查看迁移进度\n15kubectl get rfscd my-cache-deploy -o jsonpath='{.status.excludingNodes}' | jq\n16\n17# 详细负载查看（如果部署组已经Ready，可以不用关注）\n18# 查看 部署组的实际负载Pod\n19kubectl get pods -l rapidfs.baidu.com/instance=my-cache-deploy\n20\n21# 查看 部署组的实际负载Pod 详情\n22kubectl describe pod <pod-name>\n23\n24# 查看 部署组的实际负载Pod 日志\n25kubectl logs <pod-name> -c app
\n
\n
\n
\n \n

4.2 部署组状态说明

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Phase说明处理建议
Starting正在创建 Pod等待 Pod 启动
Ready所有 Pod 就绪正常运行
Partial部分 Pod 未就绪检查 Pod 状态
Scaling正在缩容等待数据迁移完成
PermissionDenied无操作权限检查权限配置
\n

五、常用运维操作

\n

5.1 部署组扩容

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1# 将副本数从 10 扩容到 15\n2spec:\n3  replicas: 15\n4  rapidfsToken: "your-token"
\n
\n
\n
\n \n

5.2 部署组缩容（普通缩容）

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1# 将副本数从 15 缩容到 10\n2spec:\n3  replicas: 10\n4  rapidfsToken: "your-token"
\n
\n
\n
\n \n
\n

普通缩容会随机选择节点下线，不保证数据安全

\n
\n

5.3 指定节点缩容（带数据迁移）

\n

场景：下线指定节点，确保数据安全迁移

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1spec:\n2  replicas: 9                         # 目标副本数\n3  rapidfsToken: "your-token"\n4  excludeNodeGroup:                   # 要下线的节点列表\n5  - "node-1"\n6  - "node-2"
\n
\n
\n
\n \n

流程说明：

\n
    \n
  1. RapidFS 自动迁移数据到其他节点
    2. \n
  2. 迁移完成后，删除对应 Pod，并从 excludeNodeGroup 中移除已下线节点
    3. \n
\n

查看迁移进度：

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1kubectl get rfscd my-cache-deploy -o jsonpath='{.status.excludingNodes}'
\n
\n
\n
\n \n

5.4 节点迁移

\n

场景： 节点维护前，迁移数据到其他节点，建议用户结合部署组亲和性自行进行定向迁移

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1spec:\n2  replicas: 10                        # 副本数不变\n3  excludeNodeGroup:                   # 指定迁移源节点\n4  - "node-to-migrate"
\n
\n
\n
\n \n

迁移完成后：

\n\n
\n
\n
\n YAML\n \n
\n
\n 
1spec:\n2  replicas: 10\n3  excludeNodeGroup: []                # 清空列表
\n
\n
\n
\n \n

5.5 更新调度策略

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1# 更新节点选择器\n2kubectl patch rfscd my-cache-deploy --type=merge -p '\n3{\n4  \"spec\": {\n5    \"nodeSelector\": {\n6      \"node-type\": \"cache-ssd\"\n7    }\n8  }\n9}'\n10\n11# 更新污点容忍\n12kubectl patch rfscd my-cache-deploy --type=merge -p '\n13{\n14  \"spec\": {\n15    \"tolerations\": [\n16      {\"key\": \"dedicated\", \"operator\": \"Equal\", \"value\": \"rapidfs\", \"effect\": \"NoSchedule\"}\n17    ]\n18  }\n19}'
\n
\n
\n
\n \n

5.6 删除部署组

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1kubectl delete rfscd my-cache-deploy
\n
\n
\n
\n \n
\n

删除部署组会同时删除所有 Dataserver Pod 和相关资源，请确保数据已备份或迁移

\n
\n

六、故障排查

\n

6.1 部署组 一直处于 Starting 状态

\n

可能原因：

\n
    \n
  1. 节点资源不足
    2. \n
  2. 镜像拉取失败
    3. \n
  3. 节点调度失败
    4. \n
\n

排查步骤：

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1# 查看 Pod 状态，可能是亲和性不满足、污点容忍不满足、节点选择不满足\n2kubectl get pods -l rapidfs.baidu.com/cachedeploy=my-cache-deploy\n3\n4# 查看 Pending Pod 原因\n5kubectl describe pod <pending-pod> | grep -A 10 Events\n6\n7# 查看节点资源，可能是节点资源不足\n8kubectl describe nodes | grep -A 5 \"Allocated resources\"
\n
\n
\n
\n \n

6.2 部署组 处于 PermissionDenied 状态

\n

可能原因：

\n
    \n
  1. rapidfsID 或 rapidfsToken 错误
    2. \n
  2. RapidFS 控制台未授权此操作
    3. \n
  3. RapidFS Cache Service安装时设置了错误的region，造成所有部署组创建/更新请求都被拒绝
    4. \n
\n

排查步骤：

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1# 查看状态信息\n2kubectl get rfscd my-cache-deploy -o jsonpath='{.status.message}'\n3\n4# 检查配置\n5kubectl get rfscd my-cache-deploy -o yaml | grep -E \"rapidfsID|rapidfsToken\"\n6\n7# 查看 RapidFS Master托管实例的token信息是否更新；
\n
\n
\n
\n \n

6.3 缩容卡在 Scaling 状态

\n

可能原因：

\n
    \n
  1. 数据迁移慢
    2. \n
  2. 网络问题
    3. \n
\n

排查步骤：

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1# 查看迁移进度\n2kubectl get rfscd my-cache-deploy -o jsonpath='{.status.excludingNodes}' | jq\n3\n4# 查看迁移节点状态\n5kubectl get rfscd my-cache-deploy -o json | jq '.status.excludingNodes[] | select(.phase==\"Decommissioning\")'\n6\n7# 查看 RapidFS Master托管实例 Cache节点管理 节点缓存数据情况
\n
\n
\n
\n \n

6.4 Pod 启动失败

\n

常见错误：

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1# 查看错误信息\n2kubectl describe pod <pod-name> | grep -A 10 \"Error\"\n3\n4# 常见错误处理\n5# 1. 端口冲突：检查节点端口占用\n6# 2. 系统参数设置失败：检查节点权限\n7# 3. 存储挂载失败：检查存储路径和权限
\n
\n
\n
\n \n

6.5 日志查看

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1# Controller 日志\n2kubectl logs -n rapidfs-system deployment/rapidfs-controller -f\n3\n4# Dataserver Pod 日志\n5kubectl logs <pod-name> -c app -f\n6\n7# InitContainer 日志\n8kubectl logs <pod-name> -c sysctl-config\n9kubectl logs <pod-name> -c port-allocator
\n
\n
\n
\n \n

七、最佳实践建议

\n

7.1 资源规划

\n
    \n
  1. 节点选择：选择高性能节点，建议使用 SSD 存储
    2. \n
  2. 资源预留：为 部署组负载 预留足够资源，避免资源争抢
    3. \n
  3. 网络规划：使用 HostNetwork，确保端口不冲突
    4. \n
\n

7.2 数据性能

\n
    \n
  1. 节点下线前确保完成缩容：节点下线前确保数据已迁移
    2. \n
  2. 使用指定节点缩容：避免普通缩容导致数据丢失
    3. \n
  3. 监控迁移进度：缩容时监控 excludingNodes 状态
    4. \n
\n

7.3 性能优化

\n
    \n
  1. 合理设置副本数：根据业务需求设置，避免过度扩容
    2. \n
  2. 优化资源配置：根据实际负载调整 CPU/内存配置
    3. \n
\n

7.4 监控告警

\n

可以配置监控指标：

\n\n

八、常见问题

\n

1.如何查看 Controller ID？

\n

答：

\n\n
\n
\n
\n Bash\n \n
\n
\n 
1kubectl get configmap rapidfs-cache-service-config -n kube-system -o yaml\n2# RapidFS缓存控制器ID: data.rapidfsCacheControllerID\n3# RapidFS缓存控制器Token: data.rapidfsCacheControllerToken
\n
\n
\n
\n \n

2.如何修改已创建 部署组 的存储配置？

\n

答：不建议修改部署组的存储配置，修改存储配置后会清理rapidfs加载的缓存数据，造成读取变慢。\n存储配置支持在线修改，目前需要手动触发Pod重建，之会应用新的配置，建议生效后发起预热。

\n

3.缩容后 excludeNodeGroup 何时清空？

\n

答：缩容完成后，Controller 会自动从 excludeNodeGroup 中移除已下线节点。

\n

4.是否支持跨 namespace 部署？

\n

答：支持。可在不同 namespace 创建 部署组。

","fields":{"slug":"zmq55eu6x","title":"RapidFS Cache Service组件使用手册","date":"2026-06-09","extractedHeadings":[]},"headings":[{"value":"一、快速入门","depth":2},{"value":"1.1 前置条件","depth":3},{"value":"1.2 部署组示例","depth":3},{"value":"1.3 创建并验证","depth":3},{"value":"二、详细部署","depth":2},{"value":"2.1 前置依赖","depth":3},{"value":"2.2 容器环境组件安装","depth":3},{"value":"2.2.1 CCE集群","depth":4},{"value":"2.2.2 自建K8s集群","depth":4},{"value":"2.3 创建 RapidFS Master 托管实例","depth":3},{"value":"2.4 创建 部署组","depth":3},{"value":"三、部署组配置说明","depth":2},{"value":"3.1 必填字段","depth":3},{"value":"3.2 存储配置（storage）","depth":3},{"value":"3.3 资源配置（resources）","depth":3},{"value":"3.4 调度配置","depth":3},{"value":"3.4.1 节点选择器（nodeSelector）","depth":4},{"value":"3.4.2 亲和性（affinity）","depth":4},{"value":"3.4.3 污点容忍（tolerations）","depth":4},{"value":"3.5 高级配置","depth":3},{"value":"3.5.1 系统配置（systemConfig）","depth":4},{"value":"3.5.2 服务配置（serviceConfig）","depth":4},{"value":"四、状态查看","depth":2},{"value":"4.1 部署组状态查看","depth":3},{"value":"4.2 部署组状态说明","depth":3},{"value":"五、常用运维操作","depth":2},{"value":"5.1 部署组扩容","depth":3},{"value":"5.2 部署组缩容（普通缩容）","depth":3},{"value":"5.3 指定节点缩容（带数据迁移）","depth":3},{"value":"5.4 节点迁移","depth":3},{"value":"5.5 更新调度策略","depth":3},{"value":"5.6 删除部署组","depth":3},{"value":"六、故障排查","depth":2},{"value":"6.1 部署组 一直处于 Starting 状态","depth":3},{"value":"6.2 部署组 处于 PermissionDenied 状态","depth":3},{"value":"6.3 缩容卡在 Scaling 状态","depth":3},{"value":"6.4 Pod 启动失败","depth":3},{"value":"6.5 日志查看","depth":3},{"value":"七、最佳实践建议","depth":2},{"value":"7.1 资源规划","depth":3},{"value":"7.2 数据性能","depth":3},{"value":"7.3 性能优化","depth":3},{"value":"7.4 监控告警","depth":3},{"value":"八、常见问题","depth":2}]}},"pageContext":{"isCreatedByStatefulCreatePages":false,"slug":"zmq55eu6x","prev":{"id":"4mq559ly4","name":"Cache节点管理","path":"4mq559ly4","filePath":"操作指南/缓存实例操作/Master托管模式/Kubernetes集群类型Cache节点/Cache节点管理.md","seo":null,"parentIds":["Em2y3slbm","Lm2y4eg8y","jmq50avi2","amq50beif"],"parents":[{"id":"Em2y3slbm","documentId":"498b5a83-eb22-45b2-a8bb-006c2c4bb271","name":"操作指南","repoName":"RAPIDFS","filePath":"操作指南","disabled":false,"path":"Em2y3slbm","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null},{"id":"Lm2y4eg8y","documentId":"fbb7a673-01a3-4fca-9e95-5150079618a8","name":"缓存实例操作","repoName":"RAPIDFS","filePath":"操作指南/缓存实例操作","disabled":false,"path":"Lm2y4eg8y","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null},{"id":"jmq50avi2","documentId":"c664837b-497e-4d8d-a793-addcc45668f7","name":"Master托管模式","repoName":"RAPIDFS","filePath":"操作指南/缓存实例操作/Master托管模式","disabled":false,"path":"jmq50avi2","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":""},{"id":"amq50beif","documentId":"3c1f1a63-ac87-4aa3-9766-2f3e4bfe9ab2","name":"Kubernetes集群类型Cache节点","repoName":"RAPIDFS","filePath":"操作指南/缓存实例操作/Master托管模式/Kubernetes集群类型Cache节点","disabled":false,"path":"amq50beif","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":""}]},"next":{"id":"Umq56d5m5","name":"百舸全托管资源池类型Cache节点","path":"Umq56d5m5","filePath":"操作指南/缓存实例操作/Master托管模式/百舸全托管资源池类型Cache节点/新建缓存实例.md","seo":null,"parentIds":["Em2y3slbm","Lm2y4eg8y","jmq50avi2","Hmq50blfh"],"parents":[{"id":"Em2y3slbm","documentId":"498b5a83-eb22-45b2-a8bb-006c2c4bb271","name":"操作指南","repoName":"RAPIDFS","filePath":"操作指南","disabled":false,"path":"Em2y3slbm","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null},{"id":"Lm2y4eg8y","documentId":"fbb7a673-01a3-4fca-9e95-5150079618a8","name":"缓存实例操作","repoName":"RAPIDFS","filePath":"操作指南/缓存实例操作","disabled":false,"path":"Lm2y4eg8y","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null},{"id":"jmq50avi2","documentId":"c664837b-497e-4d8d-a793-addcc45668f7","name":"Master托管模式","repoName":"RAPIDFS","filePath":"操作指南/缓存实例操作/Master托管模式","disabled":false,"path":"jmq50avi2","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":""},{"id":"Hmq50blfh","documentId":"b88cb7fe-c95f-4ed3-a857-6da6e6b8977d","name":"百舸全托管资源池类型Cache节点","repoName":"RAPIDFS","filePath":"操作指南/缓存实例操作/Master托管模式/百舸全托管资源池类型Cache节点","disabled":false,"path":"Hmq50blfh","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":""}]},"parents":[{"id":"Em2y3slbm","documentId":"498b5a83-eb22-45b2-a8bb-006c2c4bb271","name":"操作指南","repoName":"RAPIDFS","filePath":"操作指南","disabled":false,"path":"Em2y3slbm","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null},{"id":"Lm2y4eg8y","documentId":"fbb7a673-01a3-4fca-9e95-5150079618a8","name":"缓存实例操作","repoName":"RAPIDFS","filePath":"操作指南/缓存实例操作","disabled":false,"path":"Lm2y4eg8y","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":null},{"id":"jmq50avi2","documentId":"c664837b-497e-4d8d-a793-addcc45668f7","name":"Master托管模式","repoName":"RAPIDFS","filePath":"操作指南/缓存实例操作/Master托管模式","disabled":false,"path":"jmq50avi2","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":""},{"id":"amq50beif","documentId":"3c1f1a63-ac87-4aa3-9766-2f3e4bfe9ab2","name":"Kubernetes集群类型Cache节点","repoName":"RAPIDFS","filePath":"操作指南/缓存实例操作/Master托管模式/Kubernetes集群类型Cache节点","disabled":false,"path":"amq50beif","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":""}],"specificSeo":null}}}