Hi team, how can we change the ProfilerPort when r...
# flyte-support
h
Hi team, how can we change the ProfilerPort when running
clusterresource run
cmd? IIUC, the config is from here, then find the value from here. I have tried to add
--propeller.prof-port 10255
but it seems not working. We will also pass a server.yaml file and use it in the --config server.yaml in this command, and its content is :
Copy code
{
  "server": {
    "dataProxy": {
      "upload": {
        "storagePrefix": "upload-content"
      }
    },
    "flyteadmin": {
      "eventVersion": 1,
      "metadataStoragePrefix": [
        "metadata",
        "admin"
      ],
      "profiler_port": 10254,
      "roleNameKey": "<http://iam.amazonaws.com/role|iam.amazonaws.com/role>",
      "testing": {
        "host": "<http://flyteadmin>"
      }
    },
    "grpc": {
      "maxMessageSizeBytes": 209715200,
      "port": 8089,
      "serverReflection": true
    },
    "httpPort": 8088,
    "security": {
      "allowCors": true,
      "allowedHeaders": [
        "Content-Type",
        "flyte-authorization"
      ],
      "allowedOrigins": [
        "*"
      ],
      "secure": false,
      "useAuth": false
    }
  }
}
Two questions: 1. Is it the correct way to pass the profilerPort in this file? 2. Is it
profiler_port
the wrong name? Should we use
profilerPort
instead?