vivisidea opened a new issue #4853: URL: https://github.com/apache/skywalking/issues/4853
Please answer these questions before submitting your issue. - Why do you submit this issue? - [x] Question or discussion - [] Bug - [ ] Requirement - [ ] Feature or performance improvement ___ I deployed a skywalking instance using helm chart https://github.com/apache/skywalking-kubernetes, chart version is 2.0.0 and here is my values-es6.yml ``` # Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # Default values for skywalking. # This is a YAML-formatted file. # Declare variables to be passed into your templates. serviceAccounts: oap: oap: name: skywalking-oap image: repository: apache/skywalking-oap-server tag: 7.0.0-es6 pullPolicy: IfNotPresent storageType: elasticsearch ports: grpc: 11800 rest: 12800 replicas: 2 service: type: ClusterIP javaOpts: -Xmx2g -Xms2g antiAffinity: "soft" nodeAffinity: {} nodeSelector: {} tolerations: [] resources: {} # limits: # cpu: 8 # memory: 8Gi # requests: # cpu: 8 # memory: 4Gi # podAnnotations: # example: oap-foo envoy: als: enabled: false # more envoy ALS ,please refer to https://github.com/apache/skywalking/blob/master/docs/en/setup/envoy/als_setting.md#observe-service-mesh-through-als istio: adapter: enabled: false env: SW_STORAGE_ES_RECORD_DATA_TTL: 7 SW_STORAGE_ES_OTHER_METRIC_DATA_TTL: 7 SW_STORAGE_ES_MONTH_METRIC_DATA_TTL: 6 SW_STORAGE_ES_INDEX_SHARDS_NUMBER: 3 SW_STORAGE_ES_INDEX_REPLICAS_NUMBER: 2 TZ: Asia/Shanghai # more env, please refer to https://hub.docker.com/r/apache/skywalking-oap-server # or https://github.com/apache/skywalking-docker/blob/master/6/6.4/oap/README.md#sw_telemetry ... (the rest of the file is ignored as it does not relate to this issue) ... ``` as you can see, I config `SW_STORAGE_ES_INDEX_REPLICAS_NUMBER: 2`, as I expect all the indexes to have 2 replicas in case of elasticsearch node failure but after the `skywalking-es-init-xxxx` job completed, I found that only part of the indexes have 2 replicas  is that normal? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
