wonderful-wall-76801
04/05/2023, 10:29 AMSuppressed: org.elasticsearch.client.ResponseException: method [POST], host [http://123.123.123.123:9200], URI [/datahubpolicyindex_v2/_search?typed_keys=true&max_concurrent_shard_requests=5&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&ignore_throttled=true&search_type=query_then_fetch&batched_reduce_size=512&ccs_minimize_roundtrips=true], status line [HTTP/1.1 400 Bad Request]
{"error":{"root_cause":[{"type":"parsing_exception","reason":"[term] query does not support [case_insensitive]","line":1,"col":942}],"type":"x_content_parse_exception","reason":"[1:942] [bool] failed to parse field [must]","caused_by":{"type":"x_content_parse_exception","reason":"[1:942] [bool] failed to parse field [should]","caused_by":{"type":"x_content_parse_exception","reason":"[1:942] [bool] failed to parse field [should]","caused_by":{"type":"parsing_exception","reason":"[term] query does not support [case_insensitive]","line":1,"col":942}}}},"status":400}
How we can fix that?
Thanks a lot!
PS ElasticSearch version: 7.9.3
HelmChart version: datahub-0.2.161wonderful-wall-76801
04/05/2023, 10:44 AMwonderful-wall-76801
04/05/2023, 11:01 AMdatahub-elasticsearch-setup-job logs here:
2023/04/05 09:29:32 Waiting for: http://123.123.123.123:9200
2023/04/05 09:29:32 Received 200 from http://123.123.123.123:9200
going to use protocol: http
going to use default elastic headers
not using any prefix
datahub_analytics_enabled: true
>>> GET _opendistro/_ism/policies/datahub_usage_event_policy response code is 404
>>> creating _opendistro/_ism/policies/datahub_usage_event_policy because it doesn't exist ...
{
"policy": {
"policy_id": "datahub_usage_event_policy",
"description": "Datahub Usage Event Policy",
"default_state": "Rollover",
"schema_version": 1,
"states": [
{
"name": "Rollover",
"actions": [
{
"rollover": {
"min_index_age": "1d"
}
}
],
"transitions": [
{
"state_name": "ReadOnly",
"conditions": {
"min_index_age": "7d"
}
}
]
},
{
"name": "ReadOnly",
"actions": [
{
"read_only": {}
}
],
"transitions": [
{
"state_name": "Delete",
"conditions": {
"min_index_age": "60d"
}
}
]
},
{
"name": "Delete",
"actions": [
{
"delete": {}
}
],
"transitions": []
}
],
"ism_template": {
"index_patterns": [
"datahub_usage_event-*"
],
"priority": 100
}
}
}{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Invalid field: [ism_template] found in Policy."}],"type":"illegal_argument_exception","reason":"Invalid field: [ism_template] found in Policy."},"status":400}
>>> GET _template/datahub_usage_event_index_template response code is 200
>>> _template/datahub_usage_event_index_template already exists ✓
>>> GET datahub_usage_event-000001 response code is 200
>>> datahub_usage_event-000001 already exists ✓
2023/04/05 09:29:32 Command finished successfully.better-orange-49102
04/05/2023, 11:39 AMwonderful-wall-76801
04/05/2023, 11:42 AMwonderful-wall-76801
04/06/2023, 1:43 PMFailed to perform post authentication steps. Error message: Failed to provision user with urn urn:li:corpuser:shershov-d.
Also part of GMS logs here:
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:8080
and datahub-actions pod with:
2023/04/06 13:42:28 Problem with request: Get "http://datahub-datahub-gms:8080/health": dial tcp 10.123.123.123:8080: connect: connection refused. Sleeping 1s
2023/04/06 13:42:28 Timeout after 4m0s waiting on dependencies to become available: [http://datahub-datahub-gms:8080/health]better-orange-49102
04/07/2023, 1:26 AMbetter-orange-49102
04/07/2023, 1:27 AMastonishing-answer-96712
04/07/2023, 9:42 PMwonderful-wall-76801
04/10/2023, 1:08 PMbetter-orange-49102
04/10/2023, 1:13 PMwonderful-wall-76801
04/10/2023, 1:19 PMbetter-orange-49102
04/10/2023, 1:20 PMbetter-orange-49102
04/10/2023, 1:20 PMbetter-orange-49102
04/10/2023, 1:22 PMwonderful-wall-76801
04/10/2023, 1:22 PMwonderful-wall-76801
04/10/2023, 1:22 PMwonderful-wall-76801
04/10/2023, 1:24 PMbetter-orange-49102
04/10/2023, 1:24 PMwonderful-wall-76801
04/10/2023, 1:24 PMwonderful-wall-76801
04/11/2023, 7:38 AMbetter-orange-49102
04/11/2023, 7:59 AMwonderful-wall-76801
04/11/2023, 8:05 AMCompleted Step 1/4: UpgradeQualificationStep successfully.
Executing Step 2/4: DeleteLegacyAspectRowsStep...
Completed Step 2/4: DeleteLegacyAspectRowsStep successfully.
Executing Step 3/4: DeleteLegacyGraphRelationshipStep...
Failed to delete legacy data from graph: java.lang.ClassCastException: class com.linkedin.metadata.graph.elastic.ElasticSearchGraphService cannot be cast to class com.linkedin.metadata.graph.neo4j.Neo4jGraphService (com.linkedin.metadata.graph.elastic.ElasticSearchGraphService and com.linkedin.metadata.graph.neo4j.Neo4jGraphService are in unnamed module of loader org.springframework.boot.loader.LaunchedURLClassLoader @61a485d2)
Failed to delete legacy data from graph: java.lang.ClassCastException: class com.linkedin.metadata.graph.elastic.ElasticSearchGraphService cannot be cast to class com.linkedin.metadata.graph.neo4j.Neo4jGraphService (com.linkedin.metadata.graph.elastic.ElasticSearchGraphService and com.linkedin.metadata.graph.neo4j.Neo4jGraphService are in unnamed module of loader org.springframework.boot.loader.LaunchedURLClassLoader @61a485d2)
Failed Step 3/4: DeleteLegacyGraphRelationshipStep. Failed after 1 retries.
Exiting upgrade NoCodeDataMigrationCleanup with failure.
Upgrade NoCodeDataMigrationCleanup completed with result FAILED. Exiting...
But datahub-restore-indices-adhoc Job was working finewonderful-wall-76801
04/11/2023, 12:10 PM