Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
6.0.4
-
None
-
1
Description
Consider the following examples of DropIndex messages logged by the Query Service:
2021-03-04T13:52:09.884+00:00 [Info] DropIndex 4184753189568693271 - elapsed(2m0.859122933s), err(Fail to drop index on some indexer nodes. Error=Request timed out. Index server may still be processing this request. Please check the status after sometime or retry.
|
. If cluster or indexer is currently unavailable, the operation will automaticaly retry after cluster is back to normal.)
|
and
2021-03-04T13:57:33.293+00:00 [Info] DropIndex 11400983669702550646 - elapsed(1m28.717692153s), err(<nil>)
|
In both these cases, it would be very useful to include the index nodes that are being asked to drop the indexes, and in the first it would be especially useful to include which nodes timed out. In the first message, there is also a small typo in the word "automaticaly" -> "automatically", and it looks like this is also split across two lines too - can we get this all onto a single line as well?