Our Web Players are occasionally ‘taken down’ by rogue DXPs using up all available memory and temporary disk space. As far as we can tell, this only happens when an ‘add columns’ data transformation goes out of control due to a broken join condition - a single DXP instance can rapidly consume >150GB RAM and >100GB of temporary disk space on a web player. If we’re really unlucky, the user doesn’t realise what went wrong and will open the same DXP multiple times - we seen our entire 16 Node cluster taken out by a single rogue DXP file.
Ideally, Web Player would abort the add columns operation (or any other operation that consumes memory) when it consumed all the available RAM. Alternatively, we could configure a ‘maximum percentage of RAM’ value that a single DXP could consume.