Slow query on parquet imported from SQL Server while the external SQL server is down.

I have created a parquet file using CTAS from a MS SQL Server. The query on parquet is getting stuck in STARTING state for a long time before returning the results. We could see that drill was trying to connect to the MS SQL server from which the data was imported. The MSSQL server was down, drill

Re: Slow query on parquet imported from SQL Server while the external SQL server is down.

Can you attempt to disable to jdbc plugin (configured with SQLServer) and try the query (on parquet) when SQL Server is offline? I've seen a similar issue previously when the HBase / Hive plugin was enabled but either the plugin configuration was wrong or the underlying data source was down. On F

Re: Slow query on parquet imported from SQL Server while the external SQL server is down.

So just my opinion in reading this thread. (sorry for swooping in an opining) If a CTAS is done from any data source into Parquet files there should be NO dependency on the original data source to query the resultant Parquet files. As a Drill user, as a Drill admin, this breaks the concept

Re: Slow query on parquet imported from SQL Server while the external SQL server is down.

@John, I agree that this should work. While I am not certain, I don't think the issue is specific to a particular plugin, but the way in a query's lifecycle, the foreman attempts to initialize every enabled storage plugin before proceeding to execute the query. So when a particular plugin isn't co

Re: Slow query on parquet imported from SQL Server while the external SQL server is down.

Abhishek, Your observation is correct, we just verified that: 1. The queries run as expected(faster) with Jdbc plugin disabled. 2. Queries run as expected when the plugin's datasource is running. 3. With the datasource down, queries run very slow waiting for the connection to fail Ra

Re: Slow query on parquet imported from SQL Server while the external SQL server is down.

Thanks for the update, Rahul! On Wed, Nov 30, 2016 at 9:45 PM Rahul Raj wrote: > Abhishek, > > Your observation is correct, we just verified that: > >1. The queries run as expected(faster) with Jdbc plugin disabled. >2. Queries run as expected when the plugin's datasource is running. >

Re: Slow query on parquet imported from SQL Server while the external SQL server is down.

@Abhishek, Do you think the issue is related to any storage plugin that is enabled and not available as it applies to all queries? I guess if it's an issue where all queries are slow because the foreman is waiting to initialize ALL storage plugins, regardless of their applicability to the queried

Re: Slow query on parquet imported from SQL Server while the external SQL server is down.

AFAIK, should apply to all queries, irrespective of the source of the data or the plugins involved within the query. So when this issue occurs, I would expect any query to take long to execute. On Thu, Dec 1, 2016 at 5:47 AM John Omernik wrote: > @Abhishek, > > Do you think the issue is related

Re: Slow query on parquet imported from SQL Server while the external SQL server is down.

Yes, for every query, we build schema tree by trying to initialize all storage plugins and workspaces in them, regardless of schema configuration and/or applicability to data being queried. Go ahead and file a JIRA. We are looking into fixing this. Thanks, Padma > On Dec 1, 2016, at 8:48 AM, Ab

Re: Slow query on parquet imported from SQL Server while the external SQL server is down.

Thanks for confirming Padma. I've filed DRILL-5089 to track this issue. On Thu, Dec 1, 2016 at 9:50 AM, Padma Penumarthy wrote: > Yes, for every query, we build schema tree by trying to initialize > all storage plugins and workspaces in them, r