[jira] [Created] (IMPALA-9190) CatalogdMetaProviderTest.testPiggybackFailure is flaky

Sahil Takiar created IMPALA-9190: Summary: CatalogdMetaProviderTest.testPiggybackFailure is flaky Key: IMPALA-9190 URL: https://issues.apache.org/jira/browse/IMPALA-9190 Project: IMPALA

[jira] [Commented] (IMPALA-9187) TestExecutorGroups.test_executor_group_shutdown is flaky

[ https://issues.apache.org/jira/browse/IMPALA-9187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980408#comment-16980408 ] Sahil Takiar commented on IMPALA-9187: -- Looking at the test, I think there is a race condition. The

[jira] [Commented] (IMPALA-8991) Data loading failed in Hive with error initializing MapReduce cluster

[ https://issues.apache.org/jira/browse/IMPALA-8991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980435#comment-16980435 ] Sahil Takiar commented on IMPALA-8991: -- Saw this happen again in

[jira] [Commented] (IMPALA-9188) Dataload is failing when USE_CDP_HIVE=true

[ https://issues.apache.org/jira/browse/IMPALA-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980459#comment-16980459 ] Sahil Takiar commented on IMPALA-9188: -- IMPALA-9104 was recently merged, and I haven't found a

[jira] [Updated] (IMPALA-9188) Dataload is failing when USE_CDP_HIVE=true

[ https://issues.apache.org/jira/browse/IMPALA-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9188: - Priority: Critical (was: Major) > Dataload is failing when USE_CDP_HIVE=true >

[jira] [Commented] (IMPALA-9188) Dataload is failing when USE_CDP_HIVE=true

[ https://issues.apache.org/jira/browse/IMPALA-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980472#comment-16980472 ] Sahil Takiar commented on IMPALA-9188: -- [~vihangk1] any ideas on this? Otherwise, I think we might

[jira] [Commented] (IMPALA-9190) CatalogdMetaProviderTest.testPiggybackFailure is flaky

[ https://issues.apache.org/jira/browse/IMPALA-9190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980484#comment-16980484 ] Sahil Takiar commented on IMPALA-9190: -- Only seen once in an exhaustive build with the data cache

[jira] [Commented] (IMPALA-9188) Dataload is failing when USE_CDP_HIVE=true

[ https://issues.apache.org/jira/browse/IMPALA-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980583#comment-16980583 ] Sahil Takiar commented on IMPALA-9188: -- Looked through the HMS logs. According to the logs, the

[jira] [Updated] (IMPALA-9188) Dataload is failing when USE_CDP_HIVE=true

[ https://issues.apache.org/jira/browse/IMPALA-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9188: - Description: When USE_CDP_HIVE=true, Impala builds are failing during dataload when creating

[jira] [Commented] (IMPALA-9193) Enable precommit tests for USE_CDP_HIVE=true

[ https://issues.apache.org/jira/browse/IMPALA-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980605#comment-16980605 ] Sahil Takiar commented on IMPALA-9193: -- +1 having this in place would have prevented IMPALA-9188 >

[jira] [Commented] (IMPALA-9188) Dataload is failing when USE_CDP_HIVE=true

[ https://issues.apache.org/jira/browse/IMPALA-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980624#comment-16980624 ] Sahil Takiar commented on IMPALA-9188: -- Yeah, switching the order fixes it. Something odd is going

[jira] [Commented] (IMPALA-9188) Dataload is failing when USE_CDP_HIVE=true

[ https://issues.apache.org/jira/browse/IMPALA-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980599#comment-16980599 ] Sahil Takiar commented on IMPALA-9188: -- I'll try digging into it a bit, but if I can't figure it

[jira] [Commented] (IMPALA-9184) TestImpalaShellInteractive.test_ddl_queries_are_closed is flaky

[ https://issues.apache.org/jira/browse/IMPALA-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16979845#comment-16979845 ] Sahil Takiar commented on IMPALA-9184: -- Seen once so far on a S3 build. >

[jira] [Created] (IMPALA-9184) TestImpalaShellInteractive.test_ddl_queries_are_closed is flaky

Sahil Takiar created IMPALA-9184: Summary: TestImpalaShellInteractive.test_ddl_queries_are_closed is flaky Key: IMPALA-9184 URL: https://issues.apache.org/jira/browse/IMPALA-9184 Project: IMPALA

[jira] [Created] (IMPALA-9233) Add impalad level metrics for query retries

Sahil Takiar created IMPALA-9233: Summary: Add impalad level metrics for query retries Key: IMPALA-9233 URL: https://issues.apache.org/jira/browse/IMPALA-9233 Project: IMPALA Issue Type:

[jira] [Commented] (IMPALA-9243) Coordinator Web UI should list which executors have been blacklisted

[ https://issues.apache.org/jira/browse/IMPALA-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995308#comment-16995308 ] Sahil Takiar commented on IMPALA-9243: -- I'm actually not sure whether or not blacklisted nodes

[jira] [Commented] (IMPALA-9243) Coordinator Web UI should list which executors have been blacklisted

[ https://issues.apache.org/jira/browse/IMPALA-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995312#comment-16995312 ] Sahil Takiar commented on IMPALA-9243: -- We could even have a separate section on the /backends page

[jira] [Created] (IMPALA-9243) Coordinator Web UI should list which executors have been blacklisted

Sahil Takiar created IMPALA-9243: Summary: Coordinator Web UI should list which executors have been blacklisted Key: IMPALA-9243 URL: https://issues.apache.org/jira/browse/IMPALA-9243 Project: IMPALA

[jira] [Commented] (IMPALA-5746) Remote fragments continue to hold onto memory after stopping the coordinator daemon

[ https://issues.apache.org/jira/browse/IMPALA-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995747#comment-16995747 ] Sahil Takiar commented on IMPALA-5746: -- Looks like IMPALA-2990 fixed this. Backends try to send a

[jira] [Commented] (IMPALA-9243) Coordinator Web UI should list which executors have been blacklisted

[ https://issues.apache.org/jira/browse/IMPALA-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995911#comment-16995911 ] Sahil Takiar commented on IMPALA-9243: -- Another nice thing to have: include the reason each node

[jira] [Commented] (IMPALA-9243) Coordinator Web UI should list which executors have been blacklisted

[ https://issues.apache.org/jira/browse/IMPALA-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995913#comment-16995913 ] Sahil Takiar commented on IMPALA-9243: -- CC: [~twmarshall] > Coordinator Web UI should list which

[jira] [Commented] (IMPALA-9224) Blacklist nodes with faulty disks

[ https://issues.apache.org/jira/browse/IMPALA-9224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998666#comment-16998666 ] Sahil Takiar commented on IMPALA-9224: -- Discussed this a bit offline with Thomas. I think the

[jira] [Resolved] (IMPALA-6894) Use an internal representation of query states in ClientRequestState

[ https://issues.apache.org/jira/browse/IMPALA-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-6894. -- Fix Version/s: Impala 3.4.0 Resolution: Fixed > Use an internal representation of

[jira] [Commented] (IMPALA-8577) Crash during OpenSSLSocket.read

[ https://issues.apache.org/jira/browse/IMPALA-8577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997434#comment-16997434 ] Sahil Takiar commented on IMPALA-8577: -- The new WildFly release + AWS SDK release seemed to do the

[jira] [Created] (IMPALA-9253) Blacklist additional posix error codes for failed DataStreamService RPCs

Sahil Takiar created IMPALA-9253: Summary: Blacklist additional posix error codes for failed DataStreamService RPCs Key: IMPALA-9253 URL: https://issues.apache.org/jira/browse/IMPALA-9253 Project:

[jira] [Created] (IMPALA-9254) Queries should only be retried if all fragments fail with retryable errors

Sahil Takiar created IMPALA-9254: Summary: Queries should only be retried if all fragments fail with retryable errors Key: IMPALA-9254 URL: https://issues.apache.org/jira/browse/IMPALA-9254 Project:

[jira] [Updated] (IMPALA-6788) Abort ExecFInstance() RPC loop early after query failure

[ https://issues.apache.org/jira/browse/IMPALA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-6788: - Priority: Critical (was: Major) > Abort ExecFInstance() RPC loop early after query failure >

[jira] [Created] (IMPALA-9229) Link runtime profiles from failed and retried queries

Sahil Takiar created IMPALA-9229: Summary: Link runtime profiles from failed and retried queries Key: IMPALA-9229 URL: https://issues.apache.org/jira/browse/IMPALA-9229 Project: IMPALA Issue

[jira] [Updated] (IMPALA-9229) Link failed and retried runtime profiles

[ https://issues.apache.org/jira/browse/IMPALA-9229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9229: - Summary: Link failed and retried runtime profiles (was: Link runtime profiles from failed and

[jira] [Work started] (IMPALA-9124) Transparently retry queries that fail due to cluster membership changes

[ https://issues.apache.org/jira/browse/IMPALA-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-9124 started by Sahil Takiar. > Transparently retry queries that fail due to cluster membership changes >

[jira] [Created] (IMPALA-9230) Retried runtime profile should include some information about previous query attempts

Sahil Takiar created IMPALA-9230: Summary: Retried runtime profile should include some information about previous query attempts Key: IMPALA-9230 URL: https://issues.apache.org/jira/browse/IMPALA-9230

[jira] [Created] (IMPALA-9227) Test coverage for query retries when there is a network partition

Sahil Takiar created IMPALA-9227: Summary: Test coverage for query retries when there is a network partition Key: IMPALA-9227 URL: https://issues.apache.org/jira/browse/IMPALA-9227 Project: IMPALA

[jira] [Updated] (IMPALA-6788) Abort ExecFInstance() RPC loop early after query failure

[ https://issues.apache.org/jira/browse/IMPALA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-6788: - Priority: Major (was: Critical) > Abort ExecFInstance() RPC loop early after query failure >

[jira] [Updated] (IMPALA-8138) Re-introduce rpc debugging options

[ https://issues.apache.org/jira/browse/IMPALA-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-8138: - Priority: Critical (was: Major) > Re-introduce rpc debugging options >

[jira] [Created] (IMPALA-9224) Blacklist nodes with faulty disks

Sahil Takiar created IMPALA-9224: Summary: Blacklist nodes with faulty disks Key: IMPALA-9224 URL: https://issues.apache.org/jira/browse/IMPALA-9224 Project: IMPALA Issue Type: Improvement

[jira] [Updated] (IMPALA-9224) Blacklist nodes with faulty disks

[ https://issues.apache.org/jira/browse/IMPALA-9224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9224: - Priority: Critical (was: Major) > Blacklist nodes with faulty disks >

[jira] [Created] (IMPALA-9225) Retryable queries should spool all results before returning any to the client

Sahil Takiar created IMPALA-9225: Summary: Retryable queries should spool all results before returning any to the client Key: IMPALA-9225 URL: https://issues.apache.org/jira/browse/IMPALA-9225

[jira] [Commented] (IMPALA-6159) DataStreamSender should transparently handle some connection reset by peer

[ https://issues.apache.org/jira/browse/IMPALA-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992849#comment-16992849 ] Sahil Takiar commented on IMPALA-6159: -- [~asherman] Michael mentioned there was some more stuff to

[jira] [Created] (IMPALA-9058) S3 tests failing with FileNotFoundException getVersionMarkerItem on ../VERSION

Sahil Takiar created IMPALA-9058: Summary: S3 tests failing with FileNotFoundException getVersionMarkerItem on ../VERSION Key: IMPALA-9058 URL: https://issues.apache.org/jira/browse/IMPALA-9058

[jira] [Commented] (IMPALA-4238) custom_cluster/test_client_ssl.py TestClientSsl.test_ssl AssertionError: SIGINT was not caught by shell within 30s

[ https://issues.apache.org/jira/browse/IMPALA-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953244#comment-16953244 ] Sahil Takiar commented on IMPALA-4238: -- For whatever reason, I've seen this happen on S3

[jira] [Commented] (IMPALA-9058) S3 tests failing with FileNotFoundException getVersionMarkerItem on ../VERSION

[ https://issues.apache.org/jira/browse/IMPALA-9058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957960#comment-16957960 ] Sahil Takiar commented on IMPALA-9058: -- The builds definitely don't have HADOOP-16520 in them, will

[jira] [Commented] (IMPALA-9058) S3 tests failing with FileNotFoundException getVersionMarkerItem on ../VERSION

[ https://issues.apache.org/jira/browse/IMPALA-9058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954941#comment-16954941 ] Sahil Takiar commented on IMPALA-9058: -- [~ste...@apache.org] any ideas on this? > S3 tests failing

[jira] [Commented] (IMPALA-9032) Impala returns 0 rows over hs2-http without waiting for fetch_rows_timeout_ms timeout

[ https://issues.apache.org/jira/browse/IMPALA-9032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16977034#comment-16977034 ] Sahil Takiar commented on IMPALA-9032: -- I believe so, [~lv]? I think the related impyla issue has

[jira] [Resolved] (IMPALA-8525) preads should use hdfsPreadFully rather than hdfsPread

[ https://issues.apache.org/jira/browse/IMPALA-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-8525. -- Fix Version/s: Impala 3.4.0 Resolution: Fixed Done. Did some additional benchmarking

[jira] [Comment Edited] (IMPALA-8525) preads should use hdfsPreadFully rather than hdfsPread

[ https://issues.apache.org/jira/browse/IMPALA-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978642#comment-16978642 ] Sahil Takiar edited comment on IMPALA-8525 at 11/20/19 6:08 PM: Done.

[jira] [Commented] (IMPALA-9188) Dataload is failing when USE_CDP_HIVE=true

[ https://issues.apache.org/jira/browse/IMPALA-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16981204#comment-16981204 ] Sahil Takiar commented on IMPALA-9188: -- Uploaded a fix: https://gerrit.cloudera.org/#/c/14792/ >

[jira] [Commented] (IMPALA-9161) PlannerTest.testHbaseNoKeyEstimate failing

[ https://issues.apache.org/jira/browse/IMPALA-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16981166#comment-16981166 ] Sahil Takiar commented on IMPALA-9161: -- Saw this recently in

[jira] [Created] (IMPALA-9199) Add support for single query retries on cluster membership changes

Sahil Takiar created IMPALA-9199: Summary: Add support for single query retries on cluster membership changes Key: IMPALA-9199 URL: https://issues.apache.org/jira/browse/IMPALA-9199 Project: IMPALA

[jira] [Created] (IMPALA-9200) Add support for multi query retries on cluster membership changes

Sahil Takiar created IMPALA-9200: Summary: Add support for multi query retries on cluster membership changes Key: IMPALA-9200 URL: https://issues.apache.org/jira/browse/IMPALA-9200 Project: IMPALA

[jira] [Commented] (IMPALA-1995) Flaky test: PlannerTest.testHbase: splits for HBASE KEYRANGE not set up correctly.

[ https://issues.apache.org/jira/browse/IMPALA-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982882#comment-16982882 ] Sahil Takiar commented on IMPALA-1995: -- Again:

[jira] [Resolved] (IMPALA-9188) Dataload is failing when USE_CDP_HIVE=true

[ https://issues.apache.org/jira/browse/IMPALA-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-9188. -- Fix Version/s: Impala 3.4.0 Resolution: Fixed USE_CDP_HIVE builds are passing data

[jira] [Commented] (IMPALA-9120) Refreshing an ABFS table with a deleted directory fails

[ https://issues.apache.org/jira/browse/IMPALA-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16983059#comment-16983059 ] Sahil Takiar commented on IMPALA-9120: -- HADOOP-16685 has been fixed. Once we pull in HADOOP-16685

[jira] [Commented] (IMPALA-9152) AuthorizationStmtTest.testColumnMaskEnabled failed in precommits.

[ https://issues.apache.org/jira/browse/IMPALA-9152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986249#comment-16986249 ] Sahil Takiar commented on IMPALA-9152: -- Still happening, this time in our nightly builds:

[jira] [Commented] (IMPALA-9210) Query timeline should include entry when all query results are spooled

[ https://issues.apache.org/jira/browse/IMPALA-9210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986361#comment-16986361 ] Sahil Takiar commented on IMPALA-9210: -- CC: [~drorke] > Query timeline should include entry when

[jira] [Created] (IMPALA-9210) Query timeline should include entry when all query results are spooled

Sahil Takiar created IMPALA-9210: Summary: Query timeline should include entry when all query results are spooled Key: IMPALA-9210 URL: https://issues.apache.org/jira/browse/IMPALA-9210 Project:

[jira] [Created] (IMPALA-9209) TestRPCException.test_end_data_stream_error is flaky

Sahil Takiar created IMPALA-9209: Summary: TestRPCException.test_end_data_stream_error is flaky Key: IMPALA-9209 URL: https://issues.apache.org/jira/browse/IMPALA-9209 Project: IMPALA Issue

[jira] [Commented] (IMPALA-9209) TestRPCException.test_end_data_stream_error is flaky

[ https://issues.apache.org/jira/browse/IMPALA-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986327#comment-16986327 ] Sahil Takiar commented on IMPALA-9209: -- Only seen once so far on an exhaustive build. >

[jira] [Commented] (IMPALA-9168) TestConcurrentDdls flaky on s3 (Could not resolve table reference)

[ https://issues.apache.org/jira/browse/IMPALA-9168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16981741#comment-16981741 ] Sahil Takiar commented on IMPALA-9168: -- Saw this again, except the failure was not on S3 and

[jira] [Created] (IMPALA-9185) TestBloomFilters.test_bloom_wait_time is flaky on S3

Sahil Takiar created IMPALA-9185: Summary: TestBloomFilters.test_bloom_wait_time is flaky on S3 Key: IMPALA-9185 URL: https://issues.apache.org/jira/browse/IMPALA-9185 Project: IMPALA Issue

[jira] [Updated] (IMPALA-9113) Queries can hang if an impalad is killed after a query has FINISHED

[ https://issues.apache.org/jira/browse/IMPALA-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9113: - Description: There is a race condition in the query coordination code that could cause queries

[jira] [Resolved] (IMPALA-8656) Support for eagerly fetching and spooling all query result rows

[ https://issues.apache.org/jira/browse/IMPALA-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-8656. -- Fix Version/s: Impala 3.4.0 Resolution: Fixed Closing this and marking as Fixed. All

[jira] [Resolved] (IMPALA-8962) FETCH_ROWS_TIMEOUT_MS should apply before rows are available

[ https://issues.apache.org/jira/browse/IMPALA-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-8962. -- Fix Version/s: Impala 3.4.0 Resolution: Fixed > FETCH_ROWS_TIMEOUT_MS should apply

[jira] [Commented] (IMPALA-9032) Impala returns 0 rows over hs2-http without waiting for fetch_rows_timeout_ms timeout

[ https://issues.apache.org/jira/browse/IMPALA-9032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16947851#comment-16947851 ] Sahil Takiar commented on IMPALA-9032: -- This may or may not have been fixed in IMPALA-8962, which

[jira] [Created] (IMPALA-9004) TestCompressedFormats is broken for text files

Sahil Takiar created IMPALA-9004: Summary: TestCompressedFormats is broken for text files Key: IMPALA-9004 URL: https://issues.apache.org/jira/browse/IMPALA-9004 Project: IMPALA Issue Type:

[jira] [Commented] (IMPALA-7087) Impala is unable to read Parquet decimal columns with lower precision/scale than table metadata

[ https://issues.apache.org/jira/browse/IMPALA-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944016#comment-16944016 ] Sahil Takiar commented on IMPALA-7087: -- [~ychena] I double checked, and it doesn't look like this

[jira] [Resolved] (IMPALA-8950) Add -d and -f option to copyFromLocal and re-enable disabled S3 tests

[ https://issues.apache.org/jira/browse/IMPALA-8950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-8950. -- Fix Version/s: Impala 3.4.0 Resolution: Fixed > Add -d and -f option to copyFromLocal

[jira] [Reopened] (IMPALA-8950) Add -d and -f option to copyFromLocal and re-enable disabled S3 tests

[ https://issues.apache.org/jira/browse/IMPALA-8950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar reopened IMPALA-8950: -- This is breaking some S3 tests, so re-opening. > Add -d and -f option to copyFromLocal and

[jira] [Resolved] (IMPALA-7117) Lower debug level for HDFS S3 connector back to INFO

[ https://issues.apache.org/jira/browse/IMPALA-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-7117. -- Fix Version/s: Impala 3.4.0 Resolution: Fixed > Lower debug level for HDFS S3

[jira] [Resolved] (IMPALA-9137) Blacklist node if a DataStreamService RPC to the node fails

[ https://issues.apache.org/jira/browse/IMPALA-9137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-9137. -- Fix Version/s: Impala 3.4.0 Resolution: Fixed > Blacklist node if a DataStreamService

[jira] [Resolved] (IMPALA-9138) Classify certain errors as retryable

[ https://issues.apache.org/jira/browse/IMPALA-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-9138. -- Resolution: Won't Fix As discussed in [https://gerrit.cloudera.org/#/c/14882/], we decided to

[jira] [Created] (IMPALA-9439) Add kudu support to single_node_perf_run.py

Sahil Takiar created IMPALA-9439: Summary: Add kudu support to single_node_perf_run.py Key: IMPALA-9439 URL: https://issues.apache.org/jira/browse/IMPALA-9439 Project: IMPALA Issue Type:

[jira] [Created] (IMPALA-9441) TestHS2.test_get_schemas is flaky

Sahil Takiar created IMPALA-9441: Summary: TestHS2.test_get_schemas is flaky Key: IMPALA-9441 URL: https://issues.apache.org/jira/browse/IMPALA-9441 Project: IMPALA Issue Type: Test

[jira] [Created] (IMPALA-9442) Add Ozone to minicluster

Sahil Takiar created IMPALA-9442: Summary: Add Ozone to minicluster Key: IMPALA-9442 URL: https://issues.apache.org/jira/browse/IMPALA-9442 Project: IMPALA Issue Type: Sub-task

[jira] [Commented] (IMPALA-9440) Typo in rpcz.tmpl for inbound connection metrics

[ https://issues.apache.org/jira/browse/IMPALA-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049322#comment-17049322 ] Sahil Takiar commented on IMPALA-9440: -- [~joemcdonnell] are you fixing this, or is this a good ramp

[jira] [Resolved] (IMPALA-9313) TSAN data race in TmpFileMgr::File::Blacklist

[ https://issues.apache.org/jira/browse/IMPALA-9313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-9313. -- Fix Version/s: Impala 3.4.0 Resolution: Fixed Fixed in 

[jira] [Commented] (IMPALA-9388) Possible data race in BloomFilter::BucketFindAVX2

[ https://issues.apache.org/jira/browse/IMPALA-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049312#comment-17049312 ] Sahil Takiar commented on IMPALA-9388: -- This is likely happening because Impala doesn't add

[jira] [Commented] (IMPALA-9439) Add kudu support to single_node_perf_run.py

[ https://issues.apache.org/jira/browse/IMPALA-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049373#comment-17049373 ] Sahil Takiar commented on IMPALA-9439: -- Turns out the correct way to run this against Kudu is:

[jira] [Updated] (IMPALA-9439) Make --scale a mandatory option in single_node_perf_run.py

[ https://issues.apache.org/jira/browse/IMPALA-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9439: - Summary: Make --scale a mandatory option in single_node_perf_run.py (was: Add kudu support to

[jira] [Created] (IMPALA-9458) Improve runtime profile counters for slow IO from remote stores

Sahil Takiar created IMPALA-9458: Summary: Improve runtime profile counters for slow IO from remote stores Key: IMPALA-9458 URL: https://issues.apache.org/jira/browse/IMPALA-9458 Project: IMPALA

[jira] [Created] (IMPALA-9455) Possible data race in kudu::security::InitKerberosForServer

Sahil Takiar created IMPALA-9455: Summary: Possible data race in kudu::security::InitKerberosForServer Key: IMPALA-9455 URL: https://issues.apache.org/jira/browse/IMPALA-9455 Project: IMPALA

[jira] [Resolved] (IMPALA-9439) Make --scale a mandatory option in single_node_perf_run.py

[ https://issues.apache.org/jira/browse/IMPALA-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-9439. -- Fix Version/s: Impala 3.4.0 Resolution: Fixed > Make --scale a mandatory option in

[jira] [Commented] (IMPALA-9455) Possible data race in kudu::security::InitKerberosForServer

[ https://issues.apache.org/jira/browse/IMPALA-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049843#comment-17049843 ] Sahil Takiar commented on IMPALA-9455: -- AFAIC this is a legitimate race condition, but is unlikely

[jira] [Commented] (IMPALA-9455) Possible data race in kudu::security::InitKerberosForServer

[ https://issues.apache.org/jira/browse/IMPALA-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049856#comment-17049856 ] Sahil Takiar commented on IMPALA-9455: -- This occurs in {{RpcMgrKerberizedTest.AuthorizationFail}}

[jira] [Issue Comment Deleted] (IMPALA-9455) Possible data race in kudu::security::InitKerberosForServer

[ https://issues.apache.org/jira/browse/IMPALA-9455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9455: - Comment: was deleted (was: AFAIC this is a legitimate race condition, but is unlikely to happen

[jira] [Created] (IMPALA-9448) Test coverage for Ozone Transparent Data Encryption

Sahil Takiar created IMPALA-9448: Summary: Test coverage for Ozone Transparent Data Encryption Key: IMPALA-9448 URL: https://issues.apache.org/jira/browse/IMPALA-9448 Project: IMPALA Issue

[jira] [Created] (IMPALA-9437) Cannot get Ozone file block size after opening the file

Sahil Takiar created IMPALA-9437: Summary: Cannot get Ozone file block size after opening the file Key: IMPALA-9437 URL: https://issues.apache.org/jira/browse/IMPALA-9437 Project: IMPALA

[jira] [Commented] (IMPALA-9436) impala-shell is very slow for large query text sizes

[ https://issues.apache.org/jira/browse/IMPALA-9436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047087#comment-17047087 ] Sahil Takiar commented on IMPALA-9436: -- Should we add "upgrade sqlparse" to this list? It seems we

[jira] [Updated] (IMPALA-9340) statestore_max_missed_heartbeats is off by one

[ https://issues.apache.org/jira/browse/IMPALA-9340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9340: - Summary: statestore_max_missed_heartbeats is off by one (was: Statestore

[jira] [Created] (IMPALA-9340) Statestore statestore_max_missed_heartbeats is off by one

Sahil Takiar created IMPALA-9340: Summary: Statestore statestore_max_missed_heartbeats is off by one Key: IMPALA-9340 URL: https://issues.apache.org/jira/browse/IMPALA-9340 Project: IMPALA

[jira] [Created] (IMPALA-9339) Revise explanation of RowMaterializationTimer

Sahil Takiar created IMPALA-9339: Summary: Revise explanation of RowMaterializationTimer Key: IMPALA-9339 URL: https://issues.apache.org/jira/browse/IMPALA-9339 Project: IMPALA Issue Type:

[jira] [Created] (IMPALA-9334) Log removal of a node from the blacklist

Sahil Takiar created IMPALA-9334: Summary: Log removal of a node from the blacklist Key: IMPALA-9334 URL: https://issues.apache.org/jira/browse/IMPALA-9334 Project: IMPALA Issue Type:

[jira] [Updated] (IMPALA-9334) Log addition/removal of a node from the blacklist

[ https://issues.apache.org/jira/browse/IMPALA-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9334: - Summary: Log addition/removal of a node from the blacklist (was: Log removal of a node from

[jira] [Updated] (IMPALA-9334) Log node blacklisting removals in ClusterMembershipMgr

[ https://issues.apache.org/jira/browse/IMPALA-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9334: - Summary: Log node blacklisting removals in ClusterMembershipMgr (was: Log addition/removal of

[jira] [Updated] (IMPALA-9342) Membership updates should only remove quiescing nodes from the blacklist

[ https://issues.apache.org/jira/browse/IMPALA-9342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-9342: - Summary: Membership updates should only remove quiescing nodes from the blacklist (was:

[jira] [Commented] (IMPALA-9342) Membership updates should only remove a node from the blacklist if it is quiescing

[ https://issues.apache.org/jira/browse/IMPALA-9342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026361#comment-17026361 ] Sahil Takiar commented on IMPALA-9342: -- [~twmarshall] let me know if this makes sense. Will post a

[jira] [Created] (IMPALA-9342) Membership updates should only remove a node from the blacklist if it is quiescing

Sahil Takiar created IMPALA-9342: Summary: Membership updates should only remove a node from the blacklist if it is quiescing Key: IMPALA-9342 URL: https://issues.apache.org/jira/browse/IMPALA-9342

[jira] [Commented] (IMPALA-9314) Thrift server shutdown is racey

[ https://issues.apache.org/jira/browse/IMPALA-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030031#comment-17030031 ] Sahil Takiar commented on IMPALA-9314: -- There is a thread leak as well: {code:java} 58/114 Test

[jira] [Assigned] (IMPALA-2638) Retry queries that fail during scheduling

[ https://issues.apache.org/jira/browse/IMPALA-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar reassigned IMPALA-2638: Assignee: Sahil Takiar > Retry queries that fail during scheduling >

[jira] [Commented] (IMPALA-5746) Remote fragments continue to hold onto memory after stopping the coordinator daemon

[ https://issues.apache.org/jira/browse/IMPALA-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030876#comment-17030876 ] Sahil Takiar commented on IMPALA-5746: -- Assigning to myself to add the test case. > Remote

[jira] [Assigned] (IMPALA-5746) Remote fragments continue to hold onto memory after stopping the coordinator daemon

[ https://issues.apache.org/jira/browse/IMPALA-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar reassigned IMPALA-5746: Assignee: Sahil Takiar (was: Joe McDonnell) > Remote fragments continue to hold onto

<    2   3   4   5   6   7   8   9   10   11   >