Hi all, i have a temporal setup running in Kubernetes via the helm chart. Recently i went through the process of deleting a namespace, and recreating it. After that, i started seeing a high number of warnings from the history service pods along the lines of Unable to find namespace, process task as active . It looks like the source of the log comes from this function, although i’m unsure what this does.
my workflows are being executed fine, although i’m seeing that the CPU utilization of my history pods is slightly higher than usual
i believe it’s caused by something caching the namespace ID, as the namespace ID being logged is not the same as what’s returned by the temporal CLI (called from within the admintools pod). i’ve tried restarting all components of the temporal server, as well as the clients connecting to the server but none of these have solved the problem.has anybody seen this issue before or knows a solution to it? any advice would be greatly appreciated, thanks a lot!