Elasticsearch::Transport::Transport::Errors::BadRequest: [400]

https://sentry.gitlap.com/gitlab/gitlabcom/issues/10171/

Elasticsearch::Transport::Transport::Errors::BadRequest: [400] {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Can't specify parent if no parent field has been configured"}],"type":"illegal_argument_exception","reason":"Can't specify parent if no parent field has been configured"},"status":400}
  app/workers/elastic_indexer_worker.rb:20:in `perform'
    record.__elasticsearch__.__send__ "#{operation}_document", parent: record.es_parent
  lib/gitlab/sidekiq_middleware/request_store_middleware.rb:6:in `call'
    yield
  lib/gitlab/sidekiq_middleware/memory_killer.rb:17:in `call'
    yield
  lib/gitlab/sidekiq_middleware/arguments_logger.rb:6:in `call'
    yield
  lib/gitlab/metrics/sidekiq_middleware.rb:13:in `block in call'
    trans.run { yield }
...
(32 additional frame(s) were not displayed)

Reassigned to @vsizov

Milestone changed to %8.11

Added ~480950 label

@vsizov I'm seeing a lot of occurrences for this error, I'm assigning it to you because I know you're the Elastic master :)

mentioned in issue #21018 (closed)

I think we need to reindex Elasticsearch since the indexes have changed.

/cc: @pcarranza

Yes, it should be reindexed. But the thing is that we knew that and we disabled Elasticsearch. But it was somehow enabled.

We disabled ES for now.

Status changed to closed

This is happening again now that we started Elasticsearch again.

Status changed to reopened

Yeah, the problem is that when we added DiffNote and LegacyDiffNote models we had to let ES know about it.

This is happening again now that we started Elasticsearch again.

@stanhu Exception is the same but the reason differs. Last time it was because index has not been rebuilt.

Fix https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/818

Status changed to closed by merge request gitlab-org/gitlab-ee!818

mentioned in merge request !14785