drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhishek Girish (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DRILL-4643) Queries hang when S3 storage plugin is enabled and config is incomplete
Date Wed, 27 Apr 2016 20:44:12 GMT

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

Abhishek Girish updated DRILL-4643:
-----------------------------------
    Environment: 
Drill Version: 1.7.0
Git.Commit.ID: 5705d45095bd89fb9d1e7b3b3e12c34e74930c4c
Date: Apr 27 2016

> Queries hang when S3 storage plugin is enabled and config is incomplete
> -----------------------------------------------------------------------
>
>                 Key: DRILL-4643
>                 URL: https://issues.apache.org/jira/browse/DRILL-4643
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow, Query Planning & Optimization
>    Affects Versions: 1.7.0
>         Environment: Drill Version: 1.7.0
> Git.Commit.ID: 5705d45095bd89fb9d1e7b3b3e12c34e74930c4c
> Date: Apr 27 2016
>            Reporter: Abhishek Girish
>         Attachments: drillbit.log.txt
>
>
> I added an S3 storage plugin and was able to query files successfully. I modified the
config to remove my security keys. I might have also updated my build to 1.7.0 (from 1.6.0).
> After the change, I was unable to execute any queries. "Show schemas" and all other queries
hang and no error message was thrown. Log indicates an issue with loading the S3 classes.
> Log snippets (relevant log attached):
> {code}
> 2016-04-27 11:00:06,575 [28df01d9-7921-215c-81ec-a8ff014f4513:foreman] INFO  o.a.drill.exec.work.foreman.Foreman
- Query text for query id 28df01d9-7921-215c-81ec-a8ff014f4513: show schemas
> 2016-04-27 11:00:06,585 [drill-executor-3] ERROR o.a.d.exec.server.BootStrapContext -
org.apache.drill.exec.work.foreman.Foreman.run() leaked an exception.
> java.lang.NoClassDefFoundError: org/jets3t/service/S3ServiceException
> {code}
> After updating the S3 plugin with complete config, I was able to resolve the issue. 



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

Mime
View raw message