asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yingyi Bu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ASTERIXDB-1498) Failed to open index with resource ID after a failed query
Date Thu, 23 Jun 2016 23:04:16 GMT

    [ https://issues.apache.org/jira/browse/ASTERIXDB-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347391#comment-15347391
] 

Yingyi Bu commented on ASTERIXDB-1498:
--------------------------------------

BTW, the exception described in ASTERIXDB-1497 also happens at the end of the failed read
query.

> 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