[
https://issues.apache.org/jira/browse/ASTERIXDB-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15593440#comment-15593440
]
Ian Maxon commented on ASTERIXDB-1469:
--------------------------------------
I believe this bug might have shown itself again just today with the Cloudberry
instance, but this is the only other time I think I have seen it. The
configuration wasn't changed in this case, so it is particularly concerning.
> Non-metadata node can be bound as metadata node
> ------------------------------------------------
>
> Key: ASTERIXDB-1469
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1469
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: Configuration
> Reporter: Ian Maxon
> Assignee: Ian Maxon
> Labels: soon
>
> During metadata bootstrap, the value of the metadata node in the Metadata
> Nodegroup can actually differ from the node that is performing the process.
> This shouldn't happen unless something is wonky configuration-wise, but this
> is definitely wrong and should probably throw an error that is more clear
> than the wronlgly chosen NC being unable to find the metadata index's
> resource ID whenever a query is submitted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
