You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alias filter changes aren't getting replicated to follower cluster.
On inspecting code, the logic to replicate alias is missing code to replicate filter. This results in inconsistent alias on the follower end whenever an alias filter is updated.
for (alias in toAdd) {
log.info("Adding alias ${alias.alias} from $followerIndexName")
// Copying writeIndex from leader doesn't cause any issue as writes will be blocked anyways
request.addAliasAction(AliasActions.add().index(followerIndexName)
.alias(alias.alias)
.indexRouting(alias.indexRouting)
// Missing filter
.searchRouting(alias.searchRouting)
.writeIndex(alias.writeIndex())
.isHidden(alias.isHidden)
)
}
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the bug?
Alias filter changes aren't getting replicated to follower cluster.
On inspecting code, the logic to replicate alias is missing code to replicate filter. This results in inconsistent alias on the follower end whenever an alias filter is updated.
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
The term filter changes should propagate to follower.
The text was updated successfully, but these errors were encountered: