Just a few questions around resource exhausted. We are using the DAML on VMWare ledger. Key features of this ledger being a topology with Participant Nodes, where there can also exist Participant Nodes which are identical replicas (for fault-tolerance purposes). These participant nodes are backed by Writer/Committer nodes using a BFT consensus.
While overloading a participant node with requests, we received the following message:
Our question: Does this message occur because that particular Participant Node is overloaded or is it because the underlying Writer Nodes are overloaded? If it is just the Participant Node that is overloaded, it would mean we could switch over to a secondary Participant node, however, if it is because the underlying Writer nodes are overloaded, then switching over to a secondary would result in no benefit.
Next question, also while overloading a Participant Node, we encountered a RESOURCE_EXHAUSTED scenario which did not provide any description in the error message:
We were wondering, under what circumstances does this occur and if anyone can shed more insight into the details of whether this occurs due to an overloaded Participant Node, or because the underlying Writer Nodes are overloaded.