On Mon, Sep 3, 2018 at 7:53 AM <[email protected]> wrote: > One such service is running version 1.0.1 and we faced an issue where we > got a JVM OOM and the netty server was unable to create more threads. >
If you get a OOM, frequently the process is hosed. It is simply impossible to recover from OOMs in some parts of the code. Since every line of Java is impacted differently from an OOM, these can only be discussed on a case-by-case basis. Before that, for quite some time there were `java.io.IOException: > Connection reset by peer` exceptions (caused by a timeout configured at a > fronting Envoy setup). > That error is benign. Later versions of gRPC squelch it (hide it). -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oN_cKxwKi64Ko6%3D5rCxUqNshdYUznPDTNOaSKBUHcFFZg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
