Nigel Jones

Noticed a minor react issue with cohort display - see https://github.com/odpi/egeria-react-ui/issues/518 . However this will not prevent ship, and is not believed to be a regression

@lpalashevski FYI The 3.2.2 polymer UI looks ok at a basic level in the new charts (use --devel) - though my testing is limited to a basic asset search, lineage...

CTS tests appear successful - 5970/5970 for graph & inmem However see above issue -- issues with extracting full report The inmem profile in full: ``` inmem jq '.testLabResults.testResultsFromWorkbenches[].profileResults[] |...

Do you have further indications of what may have happened. Was anything recorded in the statefullset or pod stats (`kubectl describe`) Was the topic connector the only workload?

Also, how was the behaviour after the crash? Did the system recover? Was any data lost? Did the connector resume retrieving topics?

For example, I had an issue with my Jupyter container (a bug) which led to the container restarting and I'd see something like: ``` Containers: jupyter: Container ID: cri-o://3e6a2f6d264f9e8c6f052f23e49cb2da6a1cf35c869104c0686da689ffd2604f Image:...

If none of that helps, we probably either need to try and - examine code to guess failure - analyse/debug, check allocations when integration connector working normally, via an agent...

Just checking the log again - I presume this is the metadata server -- not where you are running the integration connector? What repository connector are you using? I'm guessing...

We have limited licenses for 'yourkit' java profiler (there are other tools available including using intellij+async profiler for example), which can help in pinning down memory issues, may be an...

@juergenhemelt I think generally we would suggest xtdb - it looks like a more scalable, reliable approach, and some performance analysis has been done on it. That being said there's...