asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murtadha Hubail (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ASTERIXDB-1498) Failed to open index with resource ID after a failed query
Date Wed, 29 Jun 2016 12:25:37 GMT

     [ https://issues.apache.org/jira/browse/ASTERIXDB-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Murtadha Hubail resolved ASTERIXDB-1498.
----------------------------------------
    Resolution: Fixed

Fixed in commit 6dc71486bb597c45151d9723f7bee0d69df27ea1.

As previously mentioned, the real cause of the issue is an uncaught exception that causes
the LifeCycleComponentManager to stop. The merged fix adds an appropriate error message when
trying to access a dataset/index after the DatasetLifeCycleManager has been stopped, so that
would make it clear that the error is not caused by the DatasetLifeCycleManager.

> Failed to open index with resource ID after a failed query
> ----------------------------------------------------------
>
>                 Key: ASTERIXDB-1498
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1498
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: Metadata
>            Reporter: Yingyi Bu
>            Assignee: Murtadha Hubail
>
> There is a read query failed and then I run into the following exception:
> {noformat}
> Caused by: org.apache.hyracks.api.exceptions.HyracksDataException: Failed to open index
with resource ID 7 since it does not exist.
>         at org.apache.asterix.common.context.DatasetLifecycleManager.open(DatasetLifecycleManager.java:191)
>         at org.apache.asterix.metadata.MetadataNode.searchIndex(MetadataNode.java:1021)
>         at org.apache.asterix.metadata.MetadataNode.getFunction(MetadataNode.java:879)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:498)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
>         at sun.rmi.transport.Transport$1.run(Transport.java:200)
>         at sun.rmi.transport.Transport$1.run(Transport.java:197)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>         ... 1 more
> {noformat}
> What could be possible reasons leading to this?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message