[
https://issues.apache.org/jira/browse/ASTERIXDB-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724737#comment-17724737
]
ASF subversion and git services commented on ASTERIXDB-3188:
------------------------------------------------------------
Commit 0f19b1ed40fbeb5ed859051b12b844abb3e2e9f2 in asterixdb's branch
refs/heads/master from Murtadha Makki Al Hubail
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=0f19b1ed40 ]
[ASTERIXDB-3188][*DB] Clear cached global resource ids on NCs
- user model changes: no
- storage format changes: no
- interface changes: yes
Details:
- Ensure any cached global resource ids on NCs are cleared after
reporting max used resource id to CC.
Change-Id: I3286915bcf313a88aaa465fa28ffeb56b3e9a0cd
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17541
Reviewed-by: Ali Alsuliman <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
> Resource ids can be reused on cc restart
> ----------------------------------------
>
> Key: ASTERIXDB-3188
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3188
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: *DB - AsterixDB
> Affects Versions: 0.9.8
> Reporter: Murtadha Makki Al Hubail
> Assignee: Murtadha Makki Al Hubail
> Priority: Major
> Labels: triaged
> Fix For: 0.9.9
>
>
> After a CC restart, NCs are currently reporting their max resource id based
> on what they have used on storage. However, they might have some cached ids
> that they should report as well. Otherwise, some resource ids could possible
> be reused across nodes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
