Possible WAL corruption on running system during K8s update

Hi, We run a dev/alpha stack of our application in Azure Kubernetes. Persistent storage is contained in Azure Files NAS storage volumes, one per server node. We ran an upgrade of Kubernetes today (from 1.24.9 to 1.26.3). During the update various pods were stopped and restarted as is normal for

Re: Ignite data region off-heap allocation

Hi Pavel, This area is confusing. There is no indication that the memory pressure applies to any individual object or allocation, so there is clearly no association between memory pressure and any particular resource. I get your argument that .Net can 'see' allocated memory. What is unclear is