2.4.1 replica set
Customer build a index on the primary as background
The secondary built the index and then got the following error
DR102 too much data written uncommitted 314.9MB

After this secondary was at 100% cpu and not reachable by other members.
I deleted the secondary data and resynced but same issue.
Then I took the server offline from replica set and deleted the added index. After that the server was fine. The logs are attached from the secondary