How to Run the Teragen-Terasort-Teravalidate Cluster Verification Tests Standalone on the BDA
(Doc ID 2037949.1)
Last updated on MARCH 25, 2017
Applies to:Big Data Appliance Integrated Software - Version 4.1.0 and later
If the Teragen-Terasort-Teravalidate cluster verification tests fail during upgrade, install, or patching or when running the cluster verifications with "./mammoth -c" running the Teragen-Terasort-Teravalidate tests standalone may facilitate debugging. This note provides steps for doing so. For example in the case of debugging a failure like:
teragen : 35 s
terasort : 3 s
teravalidate : 2 s
Total time : 40 s
Status : failed
Note: the follow options will have a performance impact on Terasort, slowing it down:
- Enable Kerberos Based Authentication true
- Enable Encrypt Hadoop Services true
- hdfs_encrypted_data_transport true
Use bdacli to tell whether any of the above are enabled:
The reason is that these security options will all slow down YARN jobs:
- bdacli getinfo cluster_kerberos_enabled
- bdacli getinfo cluster_hadoop_network_encryption_enabled
- bdacli getinfo cluster_hdfs_encryption_enabled
In addition, installing Impala typically reduces the memory available for YARN (because it needs to be reallocated to Impala) and that will significantly slow YARN down too.
Note: The terasort cluster verification is not intended for performance testing or benchmarks
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document