You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've started to see some errors with resurrectTimeout like the following: Cannot read properties of undefined (reading 'resurrectTimeout'). These seem to have started when we changed our access patterns against an index - different operations and different frequency. Haven't yet looked into any other context on them, but figured I'd go ahead and at least post here that we are seeing them.
The text was updated successfully, but these errors were encountered:
Took a quick peek at the code, seems like it's going to be one of the references after this.connections.find(), which can return undefined. Presumably there's a race condition somewhere removing the connection? I saw two references like this, in that module.
This would align with the changes we made, where we are making ES calls at a faster rate than before (when we didn't see this often). More chances for a race.
On Kibana main, using @elastic/transport 8.7.0
We've started to see some errors with
resurrectTimeout
like the following:Cannot read properties of undefined (reading 'resurrectTimeout')
. These seem to have started when we changed our access patterns against an index - different operations and different frequency. Haven't yet looked into any other context on them, but figured I'd go ahead and at least post here that we are seeing them.The text was updated successfully, but these errors were encountered: