[
https://issues.apache.org/jira/browse/IMPALA-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16501281#comment-16501281
]
ASF subversion and git services commented on IMPALA-6642:
-
Commit
[
https://issues.apache.org/jira/browse/IMPALA-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16501236#comment-16501236
]
Philip Zeyliger commented on IMPALA-7120:
-
I've had the mixed fortune of running into a similar
[
https://issues.apache.org/jira/browse/IMPALA-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16501142#comment-16501142
]
Vuk Ercegovac commented on IMPALA-6956:
---
Looking at the logs, here is a query that expired:
[
https://issues.apache.org/jira/browse/IMPALA-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500915#comment-16500915
]
Joe McDonnell commented on IMPALA-7119:
---
During dataload, we check to see that HDFS is replicating
[
https://issues.apache.org/jira/browse/IMPALA-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500899#comment-16500899
]
Tim Armstrong commented on IMPALA-7009:
---
I don't know if we have access to an Isilon machine to
[
https://issues.apache.org/jira/browse/IMPALA-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-7009:
--
Priority: Critical (was: Blocker)
> test_drop_table_with_purge fails on Isilon
>
[
https://issues.apache.org/jira/browse/IMPALA-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong reassigned IMPALA-6352:
-
Assignee: Tim Armstrong
> TestTableSample took too long in recent tests
>
[
https://issues.apache.org/jira/browse/IMPALA-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Volker updated IMPALA-7117:
Description:
This change will increase the log level for the HDFS S3 connector to DEBUG to
help
[
https://issues.apache.org/jira/browse/IMPALA-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500875#comment-16500875
]
Tim Armstrong commented on IMPALA-6642:
---
It looks like we don't get the Impalad logs for this in
Tim Armstrong created IMPALA-7119:
-
Summary: HBase tests failing with RetriesExhausted and
"RuntimeException: couldn't retrieve HBase table"
Key: IMPALA-7119
URL: https://issues.apache.org/jira/browse/IMPALA-7119
[
https://issues.apache.org/jira/browse/IMPALA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mala Chikka Kempanna updated IMPALA-7118:
-
Description:
Similar to peak node memory metric in profile like below, we also
[
https://issues.apache.org/jira/browse/IMPALA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mala Chikka Kempanna updated IMPALA-7118:
-
Description:
Similar to peak node memory metric in profile like below, we also
[
https://issues.apache.org/jira/browse/IMPALA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mala Chikka Kempanna updated IMPALA-7118:
-
Description:
Similar to peak node memory metric in profile like below, we also
[
https://issues.apache.org/jira/browse/IMPALA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mala Chikka Kempanna updated IMPALA-7118:
-
Description:
Similar to peak node memeory metric in profile like below, we also
[
https://issues.apache.org/jira/browse/IMPALA-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mala Chikka Kempanna updated IMPALA-7118:
-
Component/s: Perf Investigation
> Add mem_limit metric listing for all hosts in
Mala Chikka Kempanna created IMPALA-7118:
Summary: Add mem_limit metric listing for all hosts in the profile
Key: IMPALA-7118
URL: https://issues.apache.org/jira/browse/IMPALA-7118
Project:
[
https://issues.apache.org/jira/browse/IMPALA-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong reassigned IMPALA-6642:
-
Assignee: Tim Armstrong (was: Taras Bobrovytsky)
> start-impala-cluster.py failing in
[
https://issues.apache.org/jira/browse/IMPALA-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500813#comment-16500813
]
Thomas Tauber-Marshall commented on IMPALA-110:
---
As a general rule, we don't make
[
https://issues.apache.org/jira/browse/IMPALA-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong reassigned IMPALA-6305:
-
Assignee: Pooja Nilangekar
> Allow column definitions in ALTER VIEW
>
[
https://issues.apache.org/jira/browse/IMPALA-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong reassigned IMPALA-6835:
-
Assignee: Pooja Nilangekar
> Improve Kudu scanner error messages to include the table
[
https://issues.apache.org/jira/browse/IMPALA-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500696#comment-16500696
]
Tim Armstrong commented on IMPALA-7069:
---
I saw another crash with this backtrace:
{noformat}
CORE:
Lars Volker created IMPALA-7116:
---
Summary: Prevent tests from fetching too many results.
Key: IMPALA-7116
URL: https://issues.apache.org/jira/browse/IMPALA-7116
Project: IMPALA
Issue Type:
[
https://issues.apache.org/jira/browse/IMPALA-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-6563.
---
Resolution: Cannot Reproduce
> test_compact_catalog_updates failing to connect client
>
[
https://issues.apache.org/jira/browse/IMPALA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-7101:
-
Assignee: Dan Hecht (was: Tim Armstrong)
> Builds are timing out/hanging
>
[
https://issues.apache.org/jira/browse/IMPALA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500607#comment-16500607
]
Dan Hecht commented on IMPALA-7101:
---
Below are the relevant logs. I think what's happening is that the
[
https://issues.apache.org/jira/browse/IMPALA-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500593#comment-16500593
]
Tim Armstrong commented on IMPALA-7108:
---
So if we got rid of the precondition check, we would
[
https://issues.apache.org/jira/browse/IMPALA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500556#comment-16500556
]
Dan Hecht edited comment on IMPALA-7101 at 6/4/18 5:24 PM:
---
I reproduced a
[
https://issues.apache.org/jira/browse/IMPALA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500556#comment-16500556
]
Dan Hecht commented on IMPALA-7101:
---
I reproduced a hang by looping test_cancellation.py. After a few
[
https://issues.apache.org/jira/browse/IMPALA-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500538#comment-16500538
]
Tim Armstrong commented on IMPALA-7111:
---
Looped over the weekend with this command. Still no luck:
[
https://issues.apache.org/jira/browse/IMPALA-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500475#comment-16500475
]
ASF subversion and git services commented on IMPALA-6020:
-
Commit
[
https://issues.apache.org/jira/browse/IMPALA-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500476#comment-16500476
]
ASF subversion and git services commented on IMPALA-6020:
-
Commit
[
https://issues.apache.org/jira/browse/IMPALA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Tauber-Marshall resolved IMPALA-6937.
Resolution: Cannot Reproduce
Hasn't been seen again.
> Connection
[
https://issues.apache.org/jira/browse/IMPALA-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500159#comment-16500159
]
Zoltán Borók-Nagy edited comment on IMPALA-7108 at 6/4/18 12:41 PM:
[
https://issues.apache.org/jira/browse/IMPALA-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500159#comment-16500159
]
Zoltán Borók-Nagy commented on IMPALA-7108:
---
Yes, these kind of queries couldn't be
34 matches
Mail list logo
