Chris Gianelloni
Chris Gianelloni
It's Alpine. The musl DNS resolver is pretty terrible. It behaves differently from glibc in many ways.
This is preventing me from using schemahero on our databases.
Digging around, I ran into the `failures_before_use_standby` setting. It looks like `is_standby_exception` isn't detecting the exception correctly.
Correct. ``` 2018-07-20 18:44:27 +0000 [warn]: #0 [out_webhdfs] webhdfs check request failed. (namenode: name-1-node.hdfs.mesos:9002, error: {"RemoteException":{"exception":"StandbyException","javaClassName":"org.apache.hadoop.ipc.StandbyException","message":"Operation category READ is not supported in state standby. Visit https://s.apache.org/sbnn-error"}}) 2018-07-20 18:44:27 +0000 [warn]:...
Versions: ``` fluent-plugin-webhdfs (1.2.3) webhdfs (0.8.0) ```
Let's start with one... sqlite
I was reporting it. I may be able to work it into a sprint at work, since our project coopr would benefit greatly from this.
Unfortunately, I have been assigned to other projects at work and won't have time to look into this for quote some time.
Context, not Event/Payload.
That's not a good idea for integrity. What's possibly happening (especially on mainnet) is the application isn't shutting down in the default 30s that Docker gives as a grace period....