Re: [VOTE] 2.7.0 release candidate 3

[Tom White]

+1

I checked signature and checksums, ran RAT to check for license
headers, checked there are no binary files, verified the source tag
matches the tarball, inspected the LICENSE/NOTICE/DISCLAIMER files,
and built from source.

BTW I hit https://issues.cloudera.org/browse/IMPALA-3979, since it has
not been applied to the 2.7.0 branch. There's an easy workaround
though, so not a blocker.

Cheers,
Tom

On Thu, Sep 22, 2016 at 12:17 PM, Jim Apple  wrote:
> This vote is about whether to release Apache Impala (incubating) 2.7.0
> release candidate 3.
>
> The artifacts for testing are here:
> https://dist.apache.org/repos/dist/dev/incubator/impala/2.7.0/RC3/
>
> They correspond to the git tag 2.7.0-rc3, tree
> b93b91f67321d75754185d58c9624f5806690099
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=tree;h=b93b91f67321d75754185d58c9624f5806690099
>
> This vote will remain open for 72 hours.
>
> Anyone can vote, but only the votes of PMC members are binding.
> Available votes are +1 and -1. If there are three binding +1 votes and
> more binding +1 votes then binding -1 votes, the vote passes. If the
> vote passes, I will initiate a vote on this release candidate with the
> Incubator PMC.
>
> A +1 vote means "I have downloaded the signed source code package,
> compiled it as provided, and tested the resulting executable on my own
> platform, along with also verifying that the package meets the
> requirements of the ASF policy on releases."
>
> The ASF policy on releases is here: http://www.apache.org/dev/release.html
>
> Special extra rules for Incubator releases are here:
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
>
> -1 votes should be accompanied by a reason.
>
> After a vote, the voter should include "(binding)" or "(non-binding)"
> indicating their status as PMC members or PMC non-members. Example:
> "+1 (non-binding)"
>
> Instructions on downloading and checking the release candidate are
> available at 
> https://cwiki.apache.org/confluence/display/IMPALA/DRAFT%3A+How+to+Release

Re: Impala Toolchain Build: Unsupported options error

[Valencia Serrao]

Hi Matthew,

Thanks for the insight and the work-around you listed.

With regard kudu stub, our colleague Nishidha, had tried building it. But
we had to  face many issues with that approach.

However, we need Impala to work full-fledged on ppc64le. For that to
happen, as you also mentioned, real kudu (not kudu stub) also should work
on ppc64le. Surely, I will continue on the toolchain compilation.

Thanks once again for the quick response.

Regards,
Valencia




From:   Matthew Jacobs 
To: dev@impala.incubator.apache.org
Cc: Manish Patil/Austin/Contr/IBM@IBMUS, Sudarshan
Jagadale/Austin/Contr/IBM@IBMUS, Nishidha
Panpaliya/Austin/Contr/IBM@IBMUS, Valencia
Serrao/Austin/Contr/IBM@IBMUS
Date:   09/22/2016 09:46 PM
Subject:Re: Impala Toolchain Build: Unsupported options error



I should add that the last option about "disabling" kudu we've found
to be painful in practice and may cause you to have some issues
running/testing. If it's possible to move forward with the toolchain
compilation I would strongly recommend that.

On Thu, Sep 22, 2016 at 9:13 AM, Matthew Jacobs  wrote:
> Any modifications you make to the Kudu build would probably need to be
> checked by the folks working on the Kudu project. Impala builds Kudu
> for 2 reasons: 1) for the client which it links against (build time
> dependency) 2) for the dev environment (dev and test dependency).
>
> What are you trying to do? If you want Impala to work on ppc64le, then
> you'll probably eventually want Kudu to work on ppc64le as well, and
> that might take a lot more work/testing.
>
> If you want the impala that you build to be able to communicate with
> Kudu at all (whether or not Kudu runs on the same platform), you do
> need to compile in the client as you're currently doing. In that case,
> you should ask the Kudu authors at d...@kudu.apache.org.
>
> If you're OK with not supporting any Kudu for now, then you can
> "disable" Kudu support in the build/runtime. To do this, you should:
> 1) in native-toolchain:
> get source/kudu/build.sh  is_supported_platform() to return false
> for ppc64le
>  that results in a stub being built instead of all of kudu
> 2) in Impala: changing impala-config.sh so IS_KUDU_SUPPORTED is false
> for ppc64le.
>
> On Wed, Sep 21, 2016 at 10:45 PM, Valencia Serrao 
wrote:
>>
>> Hi All,
>>
>> I am building Impala-toolchain on ppc64le. However, while building
Kudu's
>> thirdparty "libstdc++-v3", I have encountered following errors:
>> Error1: clang-3.8: error: unsupported option '-print-multi-os-directory'
>> Error2: clang-3.8: error: unknown argument: '-mlong-double-64'
>>
>> I couldn't find any documentation to find the equivalent options to be
used
>> on ppc64le. To get around the Error1, , I have removed the
>> -print-multi-os-directory option and continued with the build.
>>
>> The build has surely progressed with this work-around, however, I need
to
>> know:
>> 1. What is the impact of removing "-print-multi-os-directory" ? Will it
>> significantly affect the functionality  for Impala ?
>> 2. Can I take the same approach for the Error2 ? What will be the impact
on
>> functionality ?
>> 3. If removing the above two options has a significant impact, then,
could
>> you share the documentation/equivalent options to be used for ppc64le ?
>>
>> Any pointers on this issue will be helpful.
>>
>> Regards,
>> Valencia

Re: Impala Toolchain Build: Unsupported options error

[Valencia Serrao]

Hi Todd,

Surely, I'm working to get kudu ported on to ppc64le. As you suggested,
I'll start the discussion thread on d...@kudu.apache.org

Regards,
Valencia


From:   Todd Lipcon 
To: "dev@impala" 
Cc: Manish Patil/Austin/Contr/IBM@IBMUS, Sudarshan
Jagadale/Austin/Contr/IBM@IBMUS, Nishidha
Panpaliya/Austin/Contr/IBM@IBMUS, Valencia
Serrao/Austin/Contr/IBM@IBMUS
Date:   09/23/2016 01:07 AM
Subject:Re: Impala Toolchain Build: Unsupported options error



Jumping in from the Kudu side: we've made no effort so far to get Kudu
running on ppc64le, and we probably have a decent amount of work to get it
stable. Given you're focusing on little-endian, it probably wouldn't be
awful, but we might be silently relying on x86's total store order in some
spots, whereas PPC's memory model is significantly weaker.

If you're interested in contributing to such a port, feel free to reach out
to d...@kudu.apache.org with any questions.

-Todd

On Thu, Sep 22, 2016 at 9:16 AM, Matthew Jacobs  wrote:
  I should add that the last option about "disabling" kudu we've found
  to be painful in practice and may cause you to have some issues
  running/testing. If it's possible to move forward with the toolchain
  compilation I would strongly recommend that.

  On Thu, Sep 22, 2016 at 9:13 AM, Matthew Jacobs  wrote:
  > Any modifications you make to the Kudu build would probably need to be
  > checked by the folks working on the Kudu project. Impala builds Kudu
  > for 2 reasons: 1) for the client which it links against (build time
  > dependency) 2) for the dev environment (dev and test dependency).
  >
  > What are you trying to do? If you want Impala to work on ppc64le, then
  > you'll probably eventually want Kudu to work on ppc64le as well, and
  > that might take a lot more work/testing.
  >
  > If you want the impala that you build to be able to communicate with
  > Kudu at all (whether or not Kudu runs on the same platform), you do
  > need to compile in the client as you're currently doing. In that case,
  > you should ask the Kudu authors at d...@kudu.apache.org.
  >
  > If you're OK with not supporting any Kudu for now, then you can
  > "disable" Kudu support in the build/runtime. To do this, you should:
  > 1) in native-toolchain:
  >     get source/kudu/build.sh  is_supported_platform() to return false
  > for ppc64le
  >      that results in a stub being built instead of all of kudu
  > 2) in Impala: changing impala-config.sh so IS_KUDU_SUPPORTED is false
  > for ppc64le.
  >
  > On Wed, Sep 21, 2016 at 10:45 PM, Valencia Serrao 
  wrote:
  >>
  >> Hi All,
  >>
  >> I am building Impala-toolchain on ppc64le. However, while building
  Kudu's
  >> thirdparty "libstdc++-v3", I have encountered following errors:
  >> Error1: clang-3.8: error: unsupported option
  '-print-multi-os-directory'
  >> Error2: clang-3.8: error: unknown argument: '-mlong-double-64'
  >>
  >> I couldn't find any documentation to find the equivalent options to be
  used
  >> on ppc64le. To get around the Error1, , I have removed the
  >> -print-multi-os-directory option and continued with the build.
  >>
  >> The build has surely progressed with this work-around, however, I need
  to
  >> know:
  >> 1. What is the impact of removing "-print-multi-os-directory" ? Will
  it
  >> significantly affect the functionality  for Impala ?
  >> 2. Can I take the same approach for the Error2 ? What will be the
  impact on
  >> functionality ?
  >> 3. If removing the above two options has a significant impact, then,
  could
  >> you share the documentation/equivalent options to be used for
  ppc64le ?
  >>
  >> Any pointers on this issue will be helpful.
  >>
  >> Regards,
  >> Valencia



--
Todd Lipcon
Software Engineer, Cloudera

Re: [VOTE] 2.7.0 release candidate 3

[Jim Apple]

+1 (non-binding)

I checked the sigs and checksums, ran RAT, checked for diffs from the
source tag, and ran the exhaustive tests.

On Fri, Sep 23, 2016 at 1:22 AM, Tom White  wrote:
> +1
>
> I checked signature and checksums, ran RAT to check for license
> headers, checked there are no binary files, verified the source tag
> matches the tarball, inspected the LICENSE/NOTICE/DISCLAIMER files,
> and built from source.
>
> BTW I hit https://issues.cloudera.org/browse/IMPALA-3979, since it has
> not been applied to the 2.7.0 branch. There's an easy workaround
> though, so not a blocker.
>
> Cheers,
> Tom
>
> On Thu, Sep 22, 2016 at 12:17 PM, Jim Apple  wrote:
>> This vote is about whether to release Apache Impala (incubating) 2.7.0
>> release candidate 3.
>>
>> The artifacts for testing are here:
>> https://dist.apache.org/repos/dist/dev/incubator/impala/2.7.0/RC3/
>>
>> They correspond to the git tag 2.7.0-rc3, tree
>> b93b91f67321d75754185d58c9624f5806690099
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=tree;h=b93b91f67321d75754185d58c9624f5806690099
>>
>> This vote will remain open for 72 hours.
>>
>> Anyone can vote, but only the votes of PMC members are binding.
>> Available votes are +1 and -1. If there are three binding +1 votes and
>> more binding +1 votes then binding -1 votes, the vote passes. If the
>> vote passes, I will initiate a vote on this release candidate with the
>> Incubator PMC.
>>
>> A +1 vote means "I have downloaded the signed source code package,
>> compiled it as provided, and tested the resulting executable on my own
>> platform, along with also verifying that the package meets the
>> requirements of the ASF policy on releases."
>>
>> The ASF policy on releases is here: http://www.apache.org/dev/release.html
>>
>> Special extra rules for Incubator releases are here:
>> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
>>
>> -1 votes should be accompanied by a reason.
>>
>> After a vote, the voter should include "(binding)" or "(non-binding)"
>> indicating their status as PMC members or PMC non-members. Example:
>> "+1 (non-binding)"
>>
>> Instructions on downloading and checking the release candidate are
>> available at 
>> https://cwiki.apache.org/confluence/display/IMPALA/DRAFT%3A+How+to+Release

Can you please send the output of these commands?

[Lars Volker]

For IMPALA-4193  I'm trying
to see how widely supported the cpufreq subsystem of sysfs is. If would
help a lot if you could run the following commands on your development
machine and send the output to me. Thanks, Lars

cat /etc/*release
uname -a
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
head -30 /proc/cpuinfo

As an example, here's the output from my dev machine:

✔ ~$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS"
NAME="Ubuntu"
VERSION="14.04.4 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.4 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
✔ ~$ uname -a
Linux lv-desktop 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22
15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
✔ ~$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
400
✔ ~$ head -30 /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
stepping: 3
microcode   : 0x1c
cpu MHz : 799.875
cache size  : 8192 KB
physical id : 0
siblings: 8
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt
bugs:
bogomips: 7183.48
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
✔ ~$

Re: Can you please send the output of these commands?

[Sailesh Mukil]

 sailesh@ubuntu:~$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
NAME="Ubuntu"
VERSION="14.04.2 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.2 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";

sailesh@ubuntu:~$ uname -a
Linux ubuntu 3.16.0-45-generic #60~14.04.1-Ubuntu SMP Fri Jul 24 21:16:23
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

sailesh@ubuntu:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
400

sailesh@ubuntu:~$ head -30 /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
stepping : 3
microcode : 0x1c
cpu MHz : 3600.000
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx
est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb
xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust bmi1 avx2 smep bmi2 erms invpcid
bogomips : 7183.16
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6

model : 60


On Fri, Sep 23, 2016 at 10:35 AM, Lars Volker  wrote:

> For IMPALA-4193  I'm
> trying
> to see how widely supported the cpufreq subsystem of sysfs is. If would
> help a lot if you could run the following commands on your development
> machine and send the output to me. Thanks, Lars
>
> cat /etc/*release
> uname -a
> cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
> head -30 /proc/cpuinfo
>
> As an example, here's the output from my dev machine:
>
> ✔ ~$ cat /etc/*release
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=14.04
> DISTRIB_CODENAME=trusty
> DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS"
> NAME="Ubuntu"
> VERSION="14.04.4 LTS, Trusty Tahr"
> ID=ubuntu
> ID_LIKE=debian
> PRETTY_NAME="Ubuntu 14.04.4 LTS"
> VERSION_ID="14.04"
> HOME_URL="http://www.ubuntu.com/";
> SUPPORT_URL="http://help.ubuntu.com/";
> BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
> ✔ ~$ uname -a
> Linux lv-desktop 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22
> 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> ✔ ~$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
> 400
> ✔ ~$ head -30 /proc/cpuinfo
> processor   : 0
> vendor_id   : GenuineIntel
> cpu family  : 6
> model   : 60
> model name  : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
> stepping: 3
> microcode   : 0x1c
> cpu MHz : 799.875
> cache size  : 8192 KB
> physical id : 0
> siblings: 8
> core id : 0
> cpu cores   : 4
> apicid  : 0
> initial apicid  : 0
> fpu : yes
> fpu_exception   : yes
> cpuid level : 13
> wp  : yes
> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
> pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
> xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
> ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
> movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida
> arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase
> tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt
> bugs:
> bogomips: 7183.48
> clflush size: 64
> cache_alignment : 64
> address sizes   : 39 bits physical, 48 bits virtual
> power management:
>
> processor   : 1
> vendor_id   : GenuineIntel
> cpu family  : 6
> ✔ ~$
>

Re: Can you please send the output of these commands?

[Tim Armstrong]

tarmstrong@tarmstrong-box:~$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu 15.10"
NAME="Ubuntu"
VERSION="15.10 (Wily Werewolf)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 15.10"
VERSION_ID="15.10"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
tarmstrong@tarmstrong-box:~$ uname -a
Linux tarmstrong-box 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:58:07
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
tarmstrong@tarmstrong-box:~$ cat
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
400
tarmstrong@tarmstrong-box:~$ head -30 /proc/cpuinfo
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 60
model name: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
stepping: 3
microcode: 0x1c
cpu MHz: 3799.968
cache size: 8192 KB
physical id: 0
siblings: 8
core id: 0
cpu cores: 4
apicid: 0
initial apicid: 0
fpu: yes
fpu_exception: yes
cpuid level: 13
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt
bugs:
bogomips: 7183.71
clflush size: 64
cache_alignment: 64
address sizes: 39 bits physical, 48 bits virtual
power management:

processor: 1
vendor_id: GenuineIntel
cpu family: 6
tarmstrong@tarmstrong-box:~$


On Fri, Sep 23, 2016 at 10:39 AM, Sailesh Mukil 
wrote:

>  sailesh@ubuntu:~$ cat /etc/*release
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=14.04
> DISTRIB_CODENAME=trusty
> DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
> NAME="Ubuntu"
> VERSION="14.04.2 LTS, Trusty Tahr"
> ID=ubuntu
> ID_LIKE=debian
> PRETTY_NAME="Ubuntu 14.04.2 LTS"
> VERSION_ID="14.04"
> HOME_URL="http://www.ubuntu.com/";
> SUPPORT_URL="http://help.ubuntu.com/";
> BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
>
> sailesh@ubuntu:~$ uname -a
> Linux ubuntu 3.16.0-45-generic #60~14.04.1-Ubuntu SMP Fri Jul 24 21:16:23
> UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> sailesh@ubuntu:~$ cat /sys/devices/system/cpu/cpu0/
> cpufreq/cpuinfo_max_freq
> 400
>
> sailesh@ubuntu:~$ head -30 /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 60
> model name : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
> stepping : 3
> microcode : 0x1c
> cpu MHz : 3600.000
> cache size : 8192 KB
> physical id : 0
> siblings : 8
> core id : 0
> cpu cores : 4
> apicid : 0
> initial apicid : 0
> fpu : yes
> fpu_exception : yes
> cpuid level : 13
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
> rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
> nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx
> est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
> tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb
> xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase
> tsc_adjust bmi1 avx2 smep bmi2 erms invpcid
> bogomips : 7183.16
> clflush size : 64
> cache_alignment : 64
> address sizes : 39 bits physical, 48 bits virtual
> power management:
>
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
>
> model : 60
>
>
> On Fri, Sep 23, 2016 at 10:35 AM, Lars Volker  wrote:
>
> > For IMPALA-4193  I'm
> > trying
> > to see how widely supported the cpufreq subsystem of sysfs is. If would
> > help a lot if you could run the following commands on your development
> > machine and send the output to me. Thanks, Lars
> >
> > cat /etc/*release
> > uname -a
> > cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
> > head -30 /proc/cpuinfo
> >
> > As an example, here's the output from my dev machine:
> >
> > ✔ ~$ cat /etc/*release
> > DISTRIB_ID=Ubuntu
> > DISTRIB_RELEASE=14.04
> > DISTRIB_CODENAME=trusty
> > DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS"
> > NAME="Ubuntu"
> > VERSION="14.04.4 LTS, Trusty Tahr"
> > ID=ubuntu
> > ID_LIKE=debian
> > PRETTY_NAME="Ubuntu 14.04.4 LTS"
> > VERSION_ID="14.04"
> > HOME_URL="http://www.ubuntu.com/";
> > SUPPORT_URL="http://help.ubuntu.com/";
> > BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
> > ✔ ~$ uname -a
> > Linux lv-desktop 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22
> > 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> > ✔ ~$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
>

Re: Can you please send the output of these commands?

[Thomas Tauber-Marshall]

thomas@thomas-desktop:~$cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS"
NAME="Ubuntu"
VERSION="14.04.4 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.4 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
thomas@thomas-desktop:~$uname -a
Linux thomas-desktop 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18
19:05:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
thomas@thomas-desktop:~$cat
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
390
thomas@thomas-desktop:~$head -30 /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
stepping: 3
microcode   : 0x17
cpu MHz : 3400.000
cache size  : 8192 KB
physical id : 0
siblings: 8
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm arat
epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm xsaveopt
bugs:
bogomips: 6784.45
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6

On Fri, Sep 23, 2016 at 10:41 AM, Tim Armstrong 
wrote:

> tarmstrong@tarmstrong-box:~$ cat /etc/*release
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=15.10
> DISTRIB_CODENAME=wily
> DISTRIB_DESCRIPTION="Ubuntu 15.10"
> NAME="Ubuntu"
> VERSION="15.10 (Wily Werewolf)"
> ID=ubuntu
> ID_LIKE=debian
> PRETTY_NAME="Ubuntu 15.10"
> VERSION_ID="15.10"
> HOME_URL="http://www.ubuntu.com/";
> SUPPORT_URL="http://help.ubuntu.com/";
> BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
> tarmstrong@tarmstrong-box:~$ uname -a
> Linux tarmstrong-box 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:58:07
> UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> tarmstrong@tarmstrong-box:~$ cat
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
> 400
> tarmstrong@tarmstrong-box:~$ head -30 /proc/cpuinfo
> processor: 0
> vendor_id: GenuineIntel
> cpu family: 6
> model: 60
> model name: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
> stepping: 3
> microcode: 0x1c
> cpu MHz: 3799.968
> cache size: 8192 KB
> physical id: 0
> siblings: 8
> core id: 0
> cpu cores: 4
> apicid: 0
> initial apicid: 0
> fpu: yes
> fpu_exception: yes
> cpuid level: 13
> wp: yes
> flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
> pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
> xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
> ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
> movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida
> arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase
> tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt
> bugs:
> bogomips: 7183.71
> clflush size: 64
> cache_alignment: 64
> address sizes: 39 bits physical, 48 bits virtual
> power management:
>
> processor: 1
> vendor_id: GenuineIntel
> cpu family: 6
> tarmstrong@tarmstrong-box:~$
>
>
> On Fri, Sep 23, 2016 at 10:39 AM, Sailesh Mukil 
> wrote:
>
> >  sailesh@ubuntu:~$ cat /etc/*release
> > DISTRIB_ID=Ubuntu
> > DISTRIB_RELEASE=14.04
> > DISTRIB_CODENAME=trusty
> > DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
> > NAME="Ubuntu"
> > VERSION="14.04.2 LTS, Trusty Tahr"
> > ID=ubuntu
> > ID_LIKE=debian
> > PRETTY_NAME="Ubuntu 14.04.2 LTS"
> > VERSION_ID="14.04"
> > HOME_URL="http://www.ubuntu.com/";
> > SUPPORT_URL="http://help.ubuntu.com/";
> > BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
> >
> > sailesh@ubuntu:~$ uname -a
> > Linux ubuntu 3.16.0-45-generic #60~14.04.1-Ubuntu SMP Fri Jul 24 21:16:23
> > UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> >
> > sailesh@ubuntu:~$ cat /sys/devices/system/cpu/cpu0/
> > cpufreq/cpuinfo_max_freq
> > 400
> >
> > sailesh@ubuntu:~$ head -30 /proc/cpuinfo
> > processor : 0
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 60
> > model name : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
> > stepping : 3
> > microcode :

[Impala-CR](cdh5-trunk) IMPALA-1702: Check all referenced tables, including those without associated TupleDescriptors, for duplicated table IDs.

[Huaisi Xu (Code Review)]

Huaisi Xu has abandoned this change.

Change subject: IMPALA-1702: Check all referenced tables, including those 
without associated TupleDescriptors, for duplicated table IDs.
..


Abandoned

Sorry just saw this.

-- 
To view, visit http://gerrit.cloudera.org:8080/2570
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: abandon
Gerrit-Change-Id: If2a6324cb9e28ba5be4bb525a639433ba3e8782b
Gerrit-PatchSet: 6
Gerrit-Project: Impala
Gerrit-Branch: cdh5-trunk
Gerrit-Owner: Huaisi Xu 
Gerrit-Reviewer: Alex Behm 
Gerrit-Reviewer: Huaisi Xu 
Gerrit-Reviewer: Jim Apple 
Gerrit-Reviewer: Marcel Kornacker 
Gerrit-Reviewer: Skye Wanderman-Milne 

Re: Can you please send the output of these commands?

[Laszlo Gaal]

This is my dev box:

laszlog@laszlog1:~$ *cat /etc/*release*

DISTRIB_ID=Ubuntu

DISTRIB_RELEASE=14.04

DISTRIB_CODENAME=trusty

DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

NAME="Ubuntu"

VERSION="14.04.5 LTS, Trusty Tahr"

ID=ubuntu

ID_LIKE=debian

PRETTY_NAME="Ubuntu 14.04.5 LTS"

VERSION_ID="14.04"

HOME_URL="http://www.ubuntu.com/";

SUPPORT_URL="http://help.ubuntu.com/";

BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";

laszlog@laszlog1:~$ *uname -a*

Linux laszlog1 3.19.0-69-generic #77~14.04.1-Ubuntu SMP Tue Aug 30 01:29:21
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

laszlog@laszlog1:~$ *cat
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq*

3301000

(probably true, the box is a DELL OptiPlex 7040 with a 3.3GHz Core i5-6600)

laszlog@laszlog1:~$ *head -30 /proc/cpuinfo*

processor : 0

vendor_id : GenuineIntel

cpu family : 6

model : 94

model name : Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz

stepping : 3

microcode : 0x74

cpu MHz : 800.000

cache size : 6144 KB

physical id : 0

siblings : 4

core id : 0

cpu cores : 4

apicid : 0

initial apicid : 0

fpu : yes

fpu_exception : yes

cpuid level : 22

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx
est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida
arat epb pln pts dtherm hwp hwp_noitfy hwp_act_window hwp_epp tpr_shadow
vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms
invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1

bugs :

bogomips : 6621.09

clflush size : 64

cache_alignment : 64

address sizes : 39 bits physical, 48 bits virtual

power management:

processor : 1

vendor_id : GenuineIntel

cpu family : 6







On Fri, Sep 23, 2016 at 7:35 PM, Lars Volker  wrote:

> For IMPALA-4193  I'm
> trying
> to see how widely supported the cpufreq subsystem of sysfs is. If would
> help a lot if you could run the following commands on your development
> machine and send the output to me. Thanks, Lars
>
> cat /etc/*release
> uname -a
> cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
> head -30 /proc/cpuinfo
>
> As an example, here's the output from my dev machine:
>
> ✔ ~$ cat /etc/*release
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=14.04
> DISTRIB_CODENAME=trusty
> DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS"
> NAME="Ubuntu"
> VERSION="14.04.4 LTS, Trusty Tahr"
> ID=ubuntu
> ID_LIKE=debian
> PRETTY_NAME="Ubuntu 14.04.4 LTS"
> VERSION_ID="14.04"
> HOME_URL="http://www.ubuntu.com/";
> SUPPORT_URL="http://help.ubuntu.com/";
> BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
> ✔ ~$ uname -a
> Linux lv-desktop 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22
> 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> ✔ ~$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
> 400
> ✔ ~$ head -30 /proc/cpuinfo
> processor   : 0
> vendor_id   : GenuineIntel
> cpu family  : 6
> model   : 60
> model name  : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
> stepping: 3
> microcode   : 0x1c
> cpu MHz : 799.875
> cache size  : 8192 KB
> physical id : 0
> siblings: 8
> core id : 0
> cpu cores   : 4
> apicid  : 0
> initial apicid  : 0
> fpu : yes
> fpu_exception   : yes
> cpuid level : 13
> wp  : yes
> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
> pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
> xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
> ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
> movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida
> arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase
> tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt
> bugs:
> bogomips: 7183.48
> clflush size: 64
> cache_alignment : 64
> address sizes   : 39 bits physical, 48 bits virtual
> power management:
>
> processor   : 1
> vendor_id   : GenuineIntel
> cpu family  : 6
> ✔ ~$
>

Re: Can you please send the output of these commands?

[Alex Behm]

abehm@tp:~/impala$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
2601000
abehm@tp:~/impala$ head -30 /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
stepping : 9
microcode : 0x16
cpu MHz : 1200.000
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16
xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx
f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi
flexpriority ept vpid fsgsbase smep erms
bogomips : 5188.22
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 58


On Fri, Sep 23, 2016 at 12:44 PM, Laszlo Gaal 
wrote:

> This is my dev box:
>
> laszlog@laszlog1:~$ *cat /etc/*release*
>
> DISTRIB_ID=Ubuntu
>
> DISTRIB_RELEASE=14.04
>
> DISTRIB_CODENAME=trusty
>
> DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"
>
> NAME="Ubuntu"
>
> VERSION="14.04.5 LTS, Trusty Tahr"
>
> ID=ubuntu
>
> ID_LIKE=debian
>
> PRETTY_NAME="Ubuntu 14.04.5 LTS"
>
> VERSION_ID="14.04"
>
> HOME_URL="http://www.ubuntu.com/";
>
> SUPPORT_URL="http://help.ubuntu.com/";
>
> BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
>
> laszlog@laszlog1:~$ *uname -a*
>
> Linux laszlog1 3.19.0-69-generic #77~14.04.1-Ubuntu SMP Tue Aug 30 01:29:21
> UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> laszlog@laszlog1:~$ *cat
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq*
>
> 3301000
>
> (probably true, the box is a DELL OptiPlex 7040 with a 3.3GHz Core i5-6600)
>
> laszlog@laszlog1:~$ *head -30 /proc/cpuinfo*
>
> processor : 0
>
> vendor_id : GenuineIntel
>
> cpu family : 6
>
> model : 94
>
> model name : Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz
>
> stepping : 3
>
> microcode : 0x74
>
> cpu MHz : 800.000
>
> cache size : 6144 KB
>
> physical id : 0
>
> siblings : 4
>
> core id : 0
>
> cpu cores : 4
>
> apicid : 0
>
> initial apicid : 0
>
> fpu : yes
>
> fpu_exception : yes
>
> cpuid level : 22
>
> wp : yes
>
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
> rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
> nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx
> est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
> tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida
> arat epb pln pts dtherm hwp hwp_noitfy hwp_act_window hwp_epp tpr_shadow
> vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms
> invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1
>
> bugs :
>
> bogomips : 6621.09
>
> clflush size : 64
>
> cache_alignment : 64
>
> address sizes : 39 bits physical, 48 bits virtual
>
> power management:
>
> processor : 1
>
> vendor_id : GenuineIntel
>
> cpu family : 6
>
>
>
>
>
>
>
> On Fri, Sep 23, 2016 at 7:35 PM, Lars Volker  wrote:
>
> > For IMPALA-4193  I'm
> > trying
> > to see how widely supported the cpufreq subsystem of sysfs is. If would
> > help a lot if you could run the following commands on your development
> > machine and send the output to me. Thanks, Lars
> >
> > cat /etc/*release
> > uname -a
> > cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
> > head -30 /proc/cpuinfo
> >
> > As an example, here's the output from my dev machine:
> >
> > ✔ ~$ cat /etc/*release
> > DISTRIB_ID=Ubuntu
> > DISTRIB_RELEASE=14.04
> > DISTRIB_CODENAME=trusty
> > DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS"
> > NAME="Ubuntu"
> > VERSION="14.04.4 LTS, Trusty Tahr"
> > ID=ubuntu
> > ID_LIKE=debian
> > PRETTY_NAME="Ubuntu 14.04.4 LTS"
> > VERSION_ID="14.04"
> > HOME_URL="http://www.ubuntu.com/";
> > SUPPORT_URL="http://help.ubuntu.com/";
> > BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
> > ✔ ~$ uname -a
> > Linux lv-desktop 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22
> > 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> > ✔ ~$ cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
> > 400
> > ✔ ~$ head -30 /proc/cpuinfo
> > processor   : 0
> > vendor_id   : GenuineIntel
> > cpu family  : 6
> > model   : 60
> > model name  : Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
> > stepping: 3
> > microcode   : 0x1c
> > cpu MHz : 799.875
> > cache size  : 8192 KB
> > physical id : 0
> > siblings: 8
> > core id : 0
> > cpu cores   : 4
> > apicid  : 0
> > 

Re: Can you please send the output of these commands?

[Yonghyun Hwang]

[pc~]  cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
400
[pc~] head -30 /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 94
model name : Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
stepping : 3
microcode : 0x74
cpu MHz : 799.929
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx
est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm
3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap
clflushopt xsaveopt xsavec xgetbv1 dtherm ida arat pln pts hwp hwp_notify
hwp_act_window hwp_epp
bugs :
bogomips : 6816.61
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6


On Fri, Sep 23, 2016 at 1:13 PM, Alex Behm  wrote:

> abehm@tp:~/impala$ cat /sys/devices/system/cpu/cpu0/
> cpufreq/cpuinfo_max_freq
> 2601000
> abehm@tp:~/impala$ head -30 /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 58
> model name : Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
> stepping : 9
> microcode : 0x16
> cpu MHz : 1200.000
> cache size : 6144 KB
> physical id : 0
> siblings : 8
> core id : 0
> cpu cores : 4
> apicid : 0
> initial apicid : 0
> fpu : yes
> fpu_exception : yes
> cpuid level : 13
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
> constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
> aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16
> xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx
> f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi
> flexpriority ept vpid fsgsbase smep erms
> bogomips : 5188.22
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
> model : 58
>
>
> On Fri, Sep 23, 2016 at 12:44 PM, Laszlo Gaal 
> wrote:
>
> > This is my dev box:
> >
> > laszlog@laszlog1:~$ *cat /etc/*release*
> >
> > DISTRIB_ID=Ubuntu
> >
> > DISTRIB_RELEASE=14.04
> >
> > DISTRIB_CODENAME=trusty
> >
> > DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"
> >
> > NAME="Ubuntu"
> >
> > VERSION="14.04.5 LTS, Trusty Tahr"
> >
> > ID=ubuntu
> >
> > ID_LIKE=debian
> >
> > PRETTY_NAME="Ubuntu 14.04.5 LTS"
> >
> > VERSION_ID="14.04"
> >
> > HOME_URL="http://www.ubuntu.com/";
> >
> > SUPPORT_URL="http://help.ubuntu.com/";
> >
> > BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
> >
> > laszlog@laszlog1:~$ *uname -a*
> >
> > Linux laszlog1 3.19.0-69-generic #77~14.04.1-Ubuntu SMP Tue Aug 30
> 01:29:21
> > UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> >
> > laszlog@laszlog1:~$ *cat
> > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq*
> >
> > 3301000
> >
> > (probably true, the box is a DELL OptiPlex 7040 with a 3.3GHz Core
> i5-6600)
> >
> > laszlog@laszlog1:~$ *head -30 /proc/cpuinfo*
> >
> > processor : 0
> >
> > vendor_id : GenuineIntel
> >
> > cpu family : 6
> >
> > model : 94
> >
> > model name : Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz
> >
> > stepping : 3
> >
> > microcode : 0x74
> >
> > cpu MHz : 800.000
> >
> > cache size : 6144 KB
> >
> > physical id : 0
> >
> > siblings : 4
> >
> > core id : 0
> >
> > cpu cores : 4
> >
> > apicid : 0
> >
> > initial apicid : 0
> >
> > fpu : yes
> >
> > fpu_exception : yes
> >
> > cpuid level : 22
> >
> > wp : yes
> >
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
> > pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
> > rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
> > nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx
> smx
> > est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
> > tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
> ida
> > arat epb pln pts dtherm hwp hwp_noitfy hwp_act_window hwp_epp tpr_shadow
> > vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2
> erms
> > invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1
> >
> > bugs :
> >
> > bogomips : 6621.09
> >
> > clflush size : 64
> >
> > cache_alignment : 64
> >
> > address sizes : 39 bits physical, 48 bits virtual
> >
> > power management:
> >
> > processor : 1
> >
> > vendor_id : GenuineIntel
> >
> > cp

Re: [VOTE] 2.7.0 release candidate 3

[Jim Apple]

It's been 36 hours, so we're halfway through the vote. No binding
votes have been cast yet (assuming mentors are not implicitly part of
the PMC)

On Fri, Sep 23, 2016 at 7:09 AM, Jim Apple  wrote:
> +1 (non-binding)
>
> I checked the sigs and checksums, ran RAT, checked for diffs from the
> source tag, and ran the exhaustive tests.
>
> On Fri, Sep 23, 2016 at 1:22 AM, Tom White  wrote:
>> +1
>>
>> I checked signature and checksums, ran RAT to check for license
>> headers, checked there are no binary files, verified the source tag
>> matches the tarball, inspected the LICENSE/NOTICE/DISCLAIMER files,
>> and built from source.
>>
>> BTW I hit https://issues.cloudera.org/browse/IMPALA-3979, since it has
>> not been applied to the 2.7.0 branch. There's an easy workaround
>> though, so not a blocker.
>>
>> Cheers,
>> Tom
>>
>> On Thu, Sep 22, 2016 at 12:17 PM, Jim Apple  wrote:
>>> This vote is about whether to release Apache Impala (incubating) 2.7.0
>>> release candidate 3.
>>>
>>> The artifacts for testing are here:
>>> https://dist.apache.org/repos/dist/dev/incubator/impala/2.7.0/RC3/
>>>
>>> They correspond to the git tag 2.7.0-rc3, tree
>>> b93b91f67321d75754185d58c9624f5806690099
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=tree;h=b93b91f67321d75754185d58c9624f5806690099
>>>
>>> This vote will remain open for 72 hours.
>>>
>>> Anyone can vote, but only the votes of PMC members are binding.
>>> Available votes are +1 and -1. If there are three binding +1 votes and
>>> more binding +1 votes then binding -1 votes, the vote passes. If the
>>> vote passes, I will initiate a vote on this release candidate with the
>>> Incubator PMC.
>>>
>>> A +1 vote means "I have downloaded the signed source code package,
>>> compiled it as provided, and tested the resulting executable on my own
>>> platform, along with also verifying that the package meets the
>>> requirements of the ASF policy on releases."
>>>
>>> The ASF policy on releases is here: http://www.apache.org/dev/release.html
>>>
>>> Special extra rules for Incubator releases are here:
>>> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
>>>
>>> -1 votes should be accompanied by a reason.
>>>
>>> After a vote, the voter should include "(binding)" or "(non-binding)"
>>> indicating their status as PMC members or PMC non-members. Example:
>>> "+1 (non-binding)"
>>>
>>> Instructions on downloading and checking the release candidate are
>>> available at 
>>> https://cwiki.apache.org/confluence/display/IMPALA/DRAFT%3A+How+to+Release

"status.cc:114] Query id 0:0 not found" every second in Impalad logs

[Mostafa Mokhtar]

Recently I started seeing what appears to be an error message followed by a
broken stack that get printed every second, the message keeps getting
printed even when there is no query running.

This appears to be coming from ImpalaServer::GetRuntimeProfileStr

or ImpalaServer::GetExecSummary


Anyone knows what is going on?

I0923 16:17:31.101012  1709 status.cc:114] Query id 0:0 not found.
@   0x84e789  (unknown)
@   0xac71b4  (unknown)
@   0xaf42ec  (unknown)
@   0xbf9815  (unknown)
@   0xbfac35  (unknown)
@   0xc0e180  (unknown)
@   0xc108fd  (unknown)
@   0xc10f8d  (unknown)
@   0x345aa079d1  (unknown)
@   0x345a6e88fd  (unknown)
I0923 16:17:32.103350  1720 status.cc:114] Query id 0:0 not found.
@   0x84e789  (unknown)
@   0xac71b4  (unknown)
@   0xaf42ec  (unknown)
@   0xbf9815  (unknown)
@   0xbfac35  (unknown)
@   0xc0e180  (unknown)
@   0xc108fd  (unknown)
@   0xc10f8d  (unknown)
@   0x345aa079d1  (unknown)
@   0x345a6e88fd  (unknown)
I0923 16:17:33.102648  1709 status.cc:114] Query id 0:0 not found.
@   0x84e789  (unknown)
@   0xac71b4  (unknown)
@   0xaf42ec  (unknown)
@   0xbf9815  (unknown)
@   0xbfac35  (unknown)
@   0xc0e180  (unknown)
@   0xc108fd  (unknown)
@   0xc10f8d  (unknown)
@   0x345aa079d1  (unknown)
@   0x345a6e88fd  (unknown)
I0923 16:17:34.103737  1720 status.cc:114] Query id 0:0 not found.
@   0x84e789  (unknown)
@   0xac71b4  (unknown)
@   0xaf42ec  (unknown)
@   0xbf9815  (unknown)
@   0xbfac35  (unknown)
@   0xc0e180  (unknown)
@   0xc108fd  (unknown)
@   0xc10f8d  (unknown)
@   0x345aa079d1  (unknown)
@   0x345a6e88fd  (unknown)
I0923 16:17:35.103298  1709 status.cc:114] Query id 0:0 not found.
@   0x84e789  (unknown)
@   0xac71b4  (unknown)
@   0xaf42ec  (unknown)
@   0xbf9815  (unknown)
@   0xbfac35  (unknown)
@   0xc0e180  (unknown)
@   0xc108fd  (unknown)
@   0xc10f8d  (unknown)
@   0x345aa079d1  (unknown)
@   0x345a6e88fd  (unknown)

Re: [VOTE] 2.7.0 release candidate 3

[Tim Armstrong]

I was able to build and run locally but I'm waiting for a longer test run
to finishing before giving +1

On Fri, Sep 23, 2016 at 4:20 PM, Jim Apple  wrote:

> It's been 36 hours, so we're halfway through the vote. No binding
> votes have been cast yet (assuming mentors are not implicitly part of
> the PMC)
>
> On Fri, Sep 23, 2016 at 7:09 AM, Jim Apple  wrote:
> > +1 (non-binding)
> >
> > I checked the sigs and checksums, ran RAT, checked for diffs from the
> > source tag, and ran the exhaustive tests.
> >
> > On Fri, Sep 23, 2016 at 1:22 AM, Tom White  wrote:
> >> +1
> >>
> >> I checked signature and checksums, ran RAT to check for license
> >> headers, checked there are no binary files, verified the source tag
> >> matches the tarball, inspected the LICENSE/NOTICE/DISCLAIMER files,
> >> and built from source.
> >>
> >> BTW I hit https://issues.cloudera.org/browse/IMPALA-3979, since it has
> >> not been applied to the 2.7.0 branch. There's an easy workaround
> >> though, so not a blocker.
> >>
> >> Cheers,
> >> Tom
> >>
> >> On Thu, Sep 22, 2016 at 12:17 PM, Jim Apple 
> wrote:
> >>> This vote is about whether to release Apache Impala (incubating) 2.7.0
> >>> release candidate 3.
> >>>
> >>> The artifacts for testing are here:
> >>> https://dist.apache.org/repos/dist/dev/incubator/impala/2.7.0/RC3/
> >>>
> >>> They correspond to the git tag 2.7.0-rc3, tree
> >>> b93b91f67321d75754185d58c9624f5806690099
> >>>
> >>> https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
> git;a=tree;h=b93b91f67321d75754185d58c9624f5806690099
> >>>
> >>> This vote will remain open for 72 hours.
> >>>
> >>> Anyone can vote, but only the votes of PMC members are binding.
> >>> Available votes are +1 and -1. If there are three binding +1 votes and
> >>> more binding +1 votes then binding -1 votes, the vote passes. If the
> >>> vote passes, I will initiate a vote on this release candidate with the
> >>> Incubator PMC.
> >>>
> >>> A +1 vote means "I have downloaded the signed source code package,
> >>> compiled it as provided, and tested the resulting executable on my own
> >>> platform, along with also verifying that the package meets the
> >>> requirements of the ASF policy on releases."
> >>>
> >>> The ASF policy on releases is here: http://www.apache.org/dev/
> release.html
> >>>
> >>> Special extra rules for Incubator releases are here:
> >>> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> >>>
> >>> -1 votes should be accompanied by a reason.
> >>>
> >>> After a vote, the voter should include "(binding)" or "(non-binding)"
> >>> indicating their status as PMC members or PMC non-members. Example:
> >>> "+1 (non-binding)"
> >>>
> >>> Instructions on downloading and checking the release candidate are
> >>> available at https://cwiki.apache.org/confluence/display/IMPALA/
> DRAFT%3A+How+to+Release
>

Re: "status.cc:114] Query id 0:0 not found" every second in Impalad logs

[Tim Armstrong]

Looks like https://issues.cloudera.org/projects/IMPALA/issues/IMPALA-3991

On Fri, Sep 23, 2016 at 4:23 PM, Mostafa Mokhtar 
wrote:

> Recently I started seeing what appears to be an error message followed by a
> broken stack that get printed every second, the message keeps getting
> printed even when there is no query running.
>
> This appears to be coming from ImpalaServer::GetRuntimeProfileStr
>  be/src/service/impala-server.cc#L589>
> or ImpalaServer::GetExecSummary
>  be/src/service/impala-server.cc#L630>
>
> Anyone knows what is going on?
>
> I0923 16:17:31.101012  1709 status.cc:114] Query id 0:0 not found.
> @   0x84e789  (unknown)
> @   0xac71b4  (unknown)
> @   0xaf42ec  (unknown)
> @   0xbf9815  (unknown)
> @   0xbfac35  (unknown)
> @   0xc0e180  (unknown)
> @   0xc108fd  (unknown)
> @   0xc10f8d  (unknown)
> @   0x345aa079d1  (unknown)
> @   0x345a6e88fd  (unknown)
> I0923 16:17:32.103350  1720 status.cc:114] Query id 0:0 not found.
> @   0x84e789  (unknown)
> @   0xac71b4  (unknown)
> @   0xaf42ec  (unknown)
> @   0xbf9815  (unknown)
> @   0xbfac35  (unknown)
> @   0xc0e180  (unknown)
> @   0xc108fd  (unknown)
> @   0xc10f8d  (unknown)
> @   0x345aa079d1  (unknown)
> @   0x345a6e88fd  (unknown)
> I0923 16:17:33.102648  1709 status.cc:114] Query id 0:0 not found.
> @   0x84e789  (unknown)
> @   0xac71b4  (unknown)
> @   0xaf42ec  (unknown)
> @   0xbf9815  (unknown)
> @   0xbfac35  (unknown)
> @   0xc0e180  (unknown)
> @   0xc108fd  (unknown)
> @   0xc10f8d  (unknown)
> @   0x345aa079d1  (unknown)
> @   0x345a6e88fd  (unknown)
> I0923 16:17:34.103737  1720 status.cc:114] Query id 0:0 not found.
> @   0x84e789  (unknown)
> @   0xac71b4  (unknown)
> @   0xaf42ec  (unknown)
> @   0xbf9815  (unknown)
> @   0xbfac35  (unknown)
> @   0xc0e180  (unknown)
> @   0xc108fd  (unknown)
> @   0xc10f8d  (unknown)
> @   0x345aa079d1  (unknown)
> @   0x345a6e88fd  (unknown)
> I0923 16:17:35.103298  1709 status.cc:114] Query id 0:0 not found.
> @   0x84e789  (unknown)
> @   0xac71b4  (unknown)
> @   0xaf42ec  (unknown)
> @   0xbf9815  (unknown)
> @   0xbfac35  (unknown)
> @   0xc0e180  (unknown)
> @   0xc108fd  (unknown)
> @   0xc10f8d  (unknown)
> @   0x345aa079d1  (unknown)
> @   0x345a6e88fd  (unknown)
>

Re: [VOTE] 2.7.0 release candidate 3

[Tim Armstrong]

+1 (binding) I was able to run all the tests, build it locally, and use
Apache rat to audit the code. nice work!

On Fri, Sep 23, 2016 at 4:31 PM, Tim Armstrong 
wrote:

> I was able to build and run locally but I'm waiting for a longer test run
> to finishing before giving +1
>
>
> On Fri, Sep 23, 2016 at 4:20 PM, Jim Apple  wrote:
>
>> It's been 36 hours, so we're halfway through the vote. No binding
>> votes have been cast yet (assuming mentors are not implicitly part of
>> the PMC)
>>
>> On Fri, Sep 23, 2016 at 7:09 AM, Jim Apple  wrote:
>> > +1 (non-binding)
>> >
>> > I checked the sigs and checksums, ran RAT, checked for diffs from the
>> > source tag, and ran the exhaustive tests.
>> >
>> > On Fri, Sep 23, 2016 at 1:22 AM, Tom White  wrote:
>> >> +1
>> >>
>> >> I checked signature and checksums, ran RAT to check for license
>> >> headers, checked there are no binary files, verified the source tag
>> >> matches the tarball, inspected the LICENSE/NOTICE/DISCLAIMER files,
>> >> and built from source.
>> >>
>> >> BTW I hit https://issues.cloudera.org/browse/IMPALA-3979, since it has
>> >> not been applied to the 2.7.0 branch. There's an easy workaround
>> >> though, so not a blocker.
>> >>
>> >> Cheers,
>> >> Tom
>> >>
>> >> On Thu, Sep 22, 2016 at 12:17 PM, Jim Apple 
>> wrote:
>> >>> This vote is about whether to release Apache Impala (incubating) 2.7.0
>> >>> release candidate 3.
>> >>>
>> >>> The artifacts for testing are here:
>> >>> https://dist.apache.org/repos/dist/dev/incubator/impala/2.7.0/RC3/
>> >>>
>> >>> They correspond to the git tag 2.7.0-rc3, tree
>> >>> b93b91f67321d75754185d58c9624f5806690099
>> >>>
>> >>> https://git-wip-us.apache.org/repos/asf?p=incubator-impala.g
>> it;a=tree;h=b93b91f67321d75754185d58c9624f5806690099
>> >>>
>> >>> This vote will remain open for 72 hours.
>> >>>
>> >>> Anyone can vote, but only the votes of PMC members are binding.
>> >>> Available votes are +1 and -1. If there are three binding +1 votes and
>> >>> more binding +1 votes then binding -1 votes, the vote passes. If the
>> >>> vote passes, I will initiate a vote on this release candidate with the
>> >>> Incubator PMC.
>> >>>
>> >>> A +1 vote means "I have downloaded the signed source code package,
>> >>> compiled it as provided, and tested the resulting executable on my own
>> >>> platform, along with also verifying that the package meets the
>> >>> requirements of the ASF policy on releases."
>> >>>
>> >>> The ASF policy on releases is here: http://www.apache.org/dev/rele
>> ase.html
>> >>>
>> >>> Special extra rules for Incubator releases are here:
>> >>> http://incubator.apache.org/incubation/Incubation_Policy.htm
>> l#Releases
>> >>>
>> >>> -1 votes should be accompanied by a reason.
>> >>>
>> >>> After a vote, the voter should include "(binding)" or "(non-binding)"
>> >>> indicating their status as PMC members or PMC non-members. Example:
>> >>> "+1 (non-binding)"
>> >>>
>> >>> Instructions on downloading and checking the release candidate are
>> >>> available at https://cwiki.apache.org/confl
>> uence/display/IMPALA/DRAFT%3A+How+to+Release
>>
>
>