You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/08/28 20:30:00 UTC
[jira] [Commented] (ASTERIXDB-2756) NullPointerException in
DatasetResourceReference.parse()
[ https://issues.apache.org/jira/browse/ASTERIXDB-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186803#comment-17186803 ]
ASF subversion and git services commented on ASTERIXDB-2756:
------------------------------------------------------------
Commit 406b304d8f837062bd88dc7e27e4304a6cafb3ce in asterixdb's branch refs/heads/master from Murtadha Makki Al Hubail
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=406b304 ]
[ASTERIXDB-2756][REP] Skip Replication of Dropped Indexes
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- When attempting to asynchronously replicate an LSM
component whose index was dropped, skip replication.
Change-Id: Ifdbf61cdfb6099af43ba2d9353dde9e8e31a4701
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/7623
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Murtadha Hubail <mh...@apache.org>
Reviewed-by: Ali Alsuliman <al...@gmail.com>
Reviewed-by: Luo Chen <cl...@uci.edu>
> NullPointerException in DatasetResourceReference.parse()
> --------------------------------------------------------
>
> Key: ASTERIXDB-2756
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2756
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: STO - Storage
> Affects Versions: 0.9.5
> Reporter: Murtadha Makki Al Hubail
> Assignee: Murtadha Makki Al Hubail
> Priority: Major
> Fix For: 0.9.5
>
>
> The following NPE was encountered during a test that creates 10 datasets then ingestion some data then create another 10 datasets and ingestion more data:
> {noformat}
> java.lang.NullPointerException: null
> at org.apache.asterix.common.storage.DatasetResourceReference.parse(DatasetResourceReference.java:55) ~[asterix-common.jar:7.0.0-0000]
> at org.apache.asterix.common.storage.DatasetResourceReference.of(DatasetResourceReference.java:38) ~[asterix-common.jar:7.0.0-0000]
> at org.apache.asterix.transaction.management.resource.PersistentLocalResourceRepository.getLocalResourceReference(PersistentLocalResourceRepository.java:352) ~[asterix-transactions.jar:7.0.0-0000]
> at org.apache.asterix.replication.management.IndexReplicationManager.skip(IndexReplicationManager.java:135) ~[asterix-replication.jar:7.0.0-0000]
> at org.apache.asterix.replication.management.IndexReplicationManager.process(IndexReplicationManager.java:104) ~[asterix-replication.jar:7.0.0-0000]
> at org.apache.asterix.replication.management.IndexReplicationManager.access$200(IndexReplicationManager.java:45) ~[asterix-replication.jar:7.0.0-0000]
> at org.apache.asterix.replication.management.IndexReplicationManager$ReplicationJobsProcessor.run(IndexReplicationManager.java:175) ~[asterix-replication.jar:7.0.0-0000]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
> {noformat}
> It looks like due to LSM lifecycle changes, some file of a disk component was deleted before we get a chance to check if it needs to be replicated or not.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)