How to modify RequestTimeout in configuration.yaml

[bighb69738]

MaxEventSize: 0
Writable:
  LogLevel: DEBUG
  Device:
    Discovery:
      Enabled: true

Service:
  Host: "localhost"
  Port: 59990
  StartupMsg: Template device started
  RequestTimeout: "20s" // Fail

Device:
  ProfilesDir: "./res/profiles"

MessageBus:
  Protocol: redis
  Host: edgex-redis
  Port: 6379
  Type: redis
  AuthMode: "usernamepassword"  # required for redis messagebus (secure or insecure)
  SecretName: redisdb
  Optional:
    ClientId: device-example

info message:
level=DEBUG ts=2023-11-27T06:45:56Z app=edgex-device-example msg="Service/RequestTimeout="5s""

[jiekechoo]

@bighb69738
There two options:

• add to docker-compose.yml

Service:
    environment:
       SERVICE_REQUESTTIMEOUT: "20s"

• the same as your configuration.yaml

here is a doc you can refer: https://docs.edgexfoundry.org/3.1/microservices/configuration/CommonEnvironmentVariables/

Jieke
YIQISOFT

[jiekechoo]

I can't fix this error. So, I'll create a new issue.

[lenny-goodell]

@jiekechoo , this is working as indented. See note at the bottom of this Docs section and my comments on the issue you created.
https://docs.edgexfoundry.org/3.1/microservices/configuration/CommonEnvironmentVariables/#service-configuration-overrides

[jiekechoo]

@bighb69738

As @lenny-intel metioned. Thanks for your help. 👍

I got the solutions.

Delete all volmues before starting docker containers.

cd compose-builder
make clean

Option 1:

add a global env in core-common-config-bootstrapper service

  core-common-config-bootstrapper:
 ...
    environment:
...
      ALL_SERVICES_SERVICE_REQUESTTIMEOUT: 60s
...

it works.

in core-metadata

in core-command

Option 2:

mount local directory ./res to container's volume /res in docker-compose.yml

    volumes:
...
      - type: bind
        source: ./res
        target: /res
        bind:
          create_host_path: true
...

and add RequestTimeout to local ./res/configuration.yaml

Service:
...
  RequestTimeout: 50s
...

finally, start docker.

docker compose -p edgex up -d

it works.

Jieke
YIQISOFT

[jiekechoo]

@lenny-intel
futhermore, it can't dynamiclly change env variables after modified the configuration.yaml, because the consul Key/Value has fixed by first starting micro services.
Can we reload all variables in configuration.yaml when user restart the services after the file modified? Then the Key/Value will replaced by new variables.

[lenny-goodell]

@jiekechoo , correct, the env override only gets applied the first time the service starts and pushes config into the Config Provider (aka Consul). On subsequent restarts the configuration is pulled from the Config Provider (env override not applied). At this point the value must be changed in the Config Provider and restart the service. Best to delete the config from the Config Provider and restart the service with Env Override or do a complete clean restart of all services to ensure the override is used.