Sid, The Hadoop level is 2.6. Sles is 11 sp3.
The libraries are there. I don't what AMS is using for its HMaster process. I will cluster setup the setup and see what I can find out. About the call when it fails. Wally -----Original Message----- From: Siddharth Wagle [mailto:[email protected]] Sent: Tuesday, March 03, 2015 10:33 AM To: [email protected] Subject: Re: AMS issue with SNAPPY Hi, The native hadoop libs have been packaged with AMS at, /usr/lib/ams-hbase/lib/hadoop-native including SNAPPY. This should be set as -Djava.library.path=/usr/lib/ams-hbase/lib/hadoop-native/, for the HMaster process. 1. What is the version of the Hadoop stack that is deployed? 2. What is the result of this operation on SLES: "which hadoop"? Would one of you like to open a Jira for this? Best Regards, Sid ________________________________________ From: Benbenek, Waldyn J <[email protected]> Sent: Tuesday, March 03, 2015 7:51 AM To: [email protected] Subject: RE: AMS issue with SNAPPY I am having this issue as well. Is this a build or an environment problem? -----Original Message----- From: Harp, Michael [mailto:[email protected]] Sent: Tuesday, February 24, 2015 4:05 PM To: [email protected] Subject: AMS issue with SNAPPY I am only able to get AMS up and running by changing timeline.metrics.hbase.compression.scheme=SNAPPY to timeline.metrics.hbase.compression.scheme=None. Any additional steps needed for snappy beyond installing snappy and snappy-devel? Environment is sles11sp1 using trunk with AMS embedded mode. Thanks, Mike 06:43:39,634 ERROR [main] PhoenixHBaseAccessor:306 - Error creating Metrics Schema in HBase using Phoenix. org.apache.phoenix.exception.PhoenixIOException: org.apache.hadoop.hbase.DoNotRetryIOException: Compression algorithm 'snappy' previously failed test.
