Marco Neumann 0173c50ba1 fix: use correct error code when querier is shutting down (#8282) ... When a long running query is in process and the querier is shutting down, it might happen that the executor (= thread pool and tokio executor responsible for the CPU-bound DataFusion execution) is shut down while the query is running. From a "systems interaction" PoV I think this is totally fine and I would like to avoid some weird ref-counting. Or in other words: if the system is shutting down, shut it down. However the error was treated as "internal" which is not useful. The client should rather be informed that its server was gone and that it is OK (and desired) to retry. So as per <https://grpc.github.io/grpc/core/md_doc_statuscodes.html> I think this should signal "unavailable". This change wires the error code in such a way that the gRPC service layer can properly inspect it and then changes the error mapping. Ref https://github.com/influxdata/idpe/issues/17917 . Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>		2023-07-20 12:08:22 +00:00
..
src	fix: use correct error code when querier is shutting down (#8282)	2023-07-20 12:08:22 +00:00
Cargo.toml	fix: use correct error code when querier is shutting down (#8282)	2023-07-20 12:08:22 +00:00