[
https://issues.apache.org/jira/browse/ASTERIXDB-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327483#comment-16327483
]
ASF subversion and git services commented on ASTERIXDB-2246:
------------------------------------------------------------
Commit 76c11424f43e62ffce4a5824e7507c9f44363047 in asterixdb's branch
refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=76c1142 ]
[ASTERIXDB-2246][STO] Ensure Metadata Cache Updated on Rebalance
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Ensure metadata cache is updated to the target
dataset by commiting the transaction before
downgrading the write lock. This prevents waiting
readers from reading a stale cache that points
to the source dataset that will be dropped.
Change-Id: I222be5d551a6dae66bf97c4bccf696f5b916d9b5
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2282
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Michael Blow <[email protected]>
> Source dataset is dropped before all queries complete during rebalance
> ----------------------------------------------------------------------
>
> Key: ASTERIXDB-2246
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2246
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: STO - Storage
> Reporter: Murtadha Hubail
> Assignee: Murtadha Hubail
> Priority: Major
>
> Source dataset is dropped before all queries complete during rebalance. The
> source dataset is supposed to be locked in write mode to drain any pending
> queries before it is switched to the rebalanced target dataset to prevent
> this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
