[
https://issues.apache.org/jira/browse/IMPALA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041601#comment-17041601
]
Tim Armstrong commented on IMPALA-4631:
---
We run a lot more tests on newer VMs/images and have
[
https://issues.apache.org/jira/browse/IMPALA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041522#comment-17041522
]
Jim Apple commented on IMPALA-4631:
---
And AWS sometimes moves VMs between physical hosts, yes? I wonder
[
https://issues.apache.org/jira/browse/IMPALA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041412#comment-17041412
]
Tim Armstrong commented on IMPALA-4631:
---
I took another look at the code.
We set
[
https://issues.apache.org/jira/browse/IMPALA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041407#comment-17041407
]
Tim Armstrong commented on IMPALA-4631:
---
I saw this again. This happened on a CentOS 6.4 vm on a
[
https://issues.apache.org/jira/browse/IMPALA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16910578#comment-16910578
]
Tim Armstrong commented on IMPALA-4631:
---
{noformat}
F0619 02:51:02.015914 9248
[
https://issues.apache.org/jira/browse/IMPALA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16910572#comment-16910572
]
Tim Armstrong commented on IMPALA-4631:
---
This happened twice in June for us. I don't have
[
https://issues.apache.org/jira/browse/IMPALA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823331#comment-16823331
]
Michael Ho commented on IMPALA-4631:
The problem still occurs after loosening the DCHECK:
[
https://issues.apache.org/jira/browse/IMPALA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16502720#comment-16502720
]
Tim Armstrong commented on IMPALA-4631:
---
This is still showing up in my flaky test JIRA search but
