typeMapfuture. The question is, retry forever or raise an exception and make the user deal with it?
Yeah, I understand. But that's the behavior that the Finagle Client has right? I mean, if I correctly understood the client already uses the
networkaddress.cache.ttl property. If that's the case I think we should do the same, so we keep the same behavior. But let's discuss more, I'll try tomorrow to take another look at it.
But, in any case, thanks for the help on fixing the issue, we were completely lost :)
jsonbwhich is not present in the default types. Please leave some feedback :)
DEBUG state machine-0 - Transitioning to state com.twitter.finagle.postgres.connection.AuthenticationRequired$ and emiting result
DEBUG c.t.f.p.c.PgClientChannelHandler - Detected channel disconnected! DEBUG c.t.f.n.c.ChannelStatsHandler - ChannelStatsHandler caught an exception INFO c.t.finagle - FailureAccrualFactory marking connection to "postgres:master" as dead.
PgClientChannelHandlerI can log it (it's a cert validation error), but I'm not sure whether that should be the responsibility of something else in the pipeline?
select nonexistentfunction(1), I get an exception back. The aforementioned
select 1however (or any other valid statement) hangs.