Collecting MustGather data for dynamic cache issues

Prepare the following MustGather information before you call HCL Support to help with dynamic cache issues.

Procedure

  1. Configure the following trace strings.
    • In the Transaction server Docker container:
      *=info:com.ibm.websphere.commerce.WC_CACHE=all:com.ibm.commerce.foundation.logging.*=all::com.ibm.commerce.dynacache.*=all:com.ibm.ws.cache.*=all:com.hcl.commerce.cache.*=all
      For information about how to set trace strings, see Configuring logging for the Transaction Server.
    • In the Search server Docker container:
      *=info: com.ibm.commerce.component.cache.*=all:com.ibm.commerce.foundation.logging.*=all:com.ibm.commerce.dynacache.*=all:com.ibm.ws.cache.*=all:com.hcl.commerce.cache.=all
      For information about how to set trace strings, Configuring logging for the Search Server.
    • In the Store server Docker container:
      *=info: com.ibm.commerce.component.cache.*=all:com.ibm.commerce.foundation.logging.*=all:com.ibm.commerce.dynacache.*=all:com.ibm.ws.cache.*=all:com.hcl.commerce.cache.*=all
      For information about how to set trace strings, Configuring logging for the Store server.
  2. Reproduce the problem.

    Record the specific steps that you used to reproduce the problem and any details that might be relevant.

  3. Collect the following files.
    • In the Transaction server Docker container:
      • /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/xml/config/com.ibm.commerce.foundation/wc-component.xml
      • /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/xml/config/com.ibm.commerce.foundation-ext/wc-component.xml (if it exists)
    • In the Search server Docker container:
      • /opt/WebSphere/Liberty/usr/servers/default/server.xml
      • /opt/WebSphere/Liberty/usr/servers/default/jvm.options
      • /opt/WebSphere/Liberty/usr/servers/default/*.log
      • /opt/WebSphere/Liberty/usr/servers/default/configDropins/overrides/jndi.xml
    • In the Store server Docker container:
      • /opt/WebSphere/Liberty/usr/servers/default/server.xml
      • /opt/WebSphere/Liberty/usr/servers/default/jvm.options
      • /opt/WebSphere/Liberty/usr/servers/default/*.log
      • /opt/WebSphere/Liberty/usr/servers/default/configDropins/overrides/jndi.xml
  4. Gather client-side caching information with the Redis server.
    1. Redis commands are used to perform some operations on the Redis server. To launch the Redis client, open the terminal and run the command redis-cli. This will establish a connection to your local server, from which you may issue any command.
    2. Access the Redis client inside the container with the following command:
      Kubectl exec -it redis-master -n redis – redis-cli
    3. Once at the Redis client command prompt, run the config get * command. This will get the configuration settings for the Redis deployment.
      127.0.0.1:6379> *config get ** 
                      
      1) "rdbchecksum"
      2) "yes"
      3) "daemonize"
      4) "no"
      5) "io-threads-do-reads"
      6) "no"
      7) "lua-replicate-commands"
      8) "yes"
      9) "always-show-logo"
      10) "no"
      11) "protected-mode"
      12) "no"
      13) "rdbcompression"
      14) "yes"
      15) "rdb-del-sync-files"
      16) "no"
      17) "activerehashing"
      18) "yes"
      19) "stop-writes-on-bgsave-error"
      20) "yes"
      ……
      291) "notify-keyspace-events"
      292) ""
      293) "bind"
      294) ""
      295) "requirepass"
      296) ""
    4. Inside the Redis pod, on the Redis client command prompt, run the Redis info command. The Redis info command returns a variety of information and statistics about a Redis server in an easy-to-understand format.
      127.0.0.1:6379> info
      Server
      redis_version:6.0.9
      redis_git_sha1:00000000
      redis_git_dirty:0
      redis_build_id:5f0299f43563a32b
      redis_mode:standalone
      os:Linux 4.18.0-240.15.1.el8_3.x86_64 x86_64
      arch_bits:64
      multiplexing_api:epoll
      atomicvar_api:atomic-builtin
      gcc_version:8.3.0
      process_id:1
      run_id:b7aaf720b88027318ac7eec5b4af54e3810f3688
      tcp_port:6379
      uptime_in_seconds:1648153
      uptime_in_days:19
      hz:10
      configured_hz:10
      lru_clock:10661649
      executable:/redis-server
      config_file:/opt/bitnami/redis/etc/redis.conf
      io_threads_active:0
                     
      Clients
      connected_clients:86
      client_recent_max_input_buffer:8
      client_recent_max_output_buffer:0
      blocked_clients:0
      tracking_clients:0
      clients_in_timeout_table:0
                     
      Memory
      used_memory:2679880
      used_memory_human:2.56M
      used_memory_rss:9031680
      used_memory_rss_human:8.61M
      used_memory_peak:5300312
      used_memory_peak_human:5.05M
      used_memory_peak_perc:50.56%
      used_memory_overhead:2571232
      used_memory_startup:803456
      used_memory_dataset:108648
      used_memory_dataset_perc:5.79%
      allocator_allocated:2801616
      allocator_active:3522560
      allocator_resident:7069696
      total_system_memory:33513758720
      total_system_memory_human:31.21G
      used_memory_lua:43008
      used_memory_lua_human:42.00K