Actually let me correct myself; regardless of what client you are using you are likely to hit this error if certain jars are not available on the appropriate class path for Pherf. Specifically I believe phoenix-server, phoenix-client and phoenix-thin-client jar should be present in the ../phoenix-client/ folder (not from the ../phoenix-client/lib folder)
HTH Gaurav On 29 February 2016 at 11:23, Gaurav Kanade <[email protected]> wrote: > Are you running Pherf with "thin" client ? In that case it is possible the > class path is missing that particular jar. > > Gaurav > > On 29 February 2016 at 10:55, Mujtaba Chohan <[email protected]> wrote: > >> This is a ClassNotFoundException. Can you make sure Phoenix jar is >> available on classpath for Pherf? If Phoenix is available in HBase/lib >> directory and HBASE_DIR environment variable is set then it should fix it. >> Also to test out first, you can run pherf_standalone.py with local HBase to >> see if everything works as expected locally before testing on cluster. >> >> On Mon, Feb 29, 2016 at 8:49 AM, Peter Savage <[email protected]> >> wrote: >> >>> Hello, >>> >>> I'm trying to setup pherf and running into a few glitches. I have been >>> using this page here: >>> >>> https://phoenix.apache.org/pherf.html >>> >>> but it appears to be slightly out of date, and I have not been able to >>> get >>> a test to run. >>> >>> We tried, using this sql - >>> >>> https://github.com/apache/phoenix/blob/master/phoenix-pherf/src/test/resources/datamodel/test_schema.sql >>> to >>> populate our schema, and then we ran against that scenario.xml, we >>> received >>> the following error: >>> >>> >>> hadoop@localhost bin]$ ./pherf-cluster.py -drop all -l -q -z localhost >>> -schemaFile >>> ../sandbox/database_schema.sql -scenarioFile ../sandbox/scenario.xml >>> >>> HBASE_DIR environment variable is currently set to: /opt/hbase >>> SLF4J: Class path contains multiple SLF4J bindings. >>> SLF4J: Found binding in >>> [jar:file:/opt/hbase/lib/slf4j-log4j12-1.7.5.jar!/org/ >>> slf4j/impl/StaticLoggerBinder.class] >>> SLF4J: Found binding in >>> [jar:file:/opt/hadoop/share/hadoop/common/lib/slf4j- >>> log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] >>> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an >>> explanation. >>> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] >>> Exception in thread "main" java.lang.NoClassDefFoundError: >>> org/apache/phoenix/schema/TableNotFoundException >>> at org.apache.phoenix.pherf.Pherf.<init>(Pherf.java:52) >>> at org.apache.phoenix.pherf.Pherf.main(Pherf.java:188) >>> Caused by: java.lang.ClassNotFoundException: >>> org.apache.phoenix.schema.TableNotFoundException >>> at java.net.URLClassLoader$1.run(URLClassLoader.java:366) >>> at java.net.URLClassLoader$1.run(URLClassLoader.java:355) >>> at java.security.AccessController.doPrivileged(Native Method) >>> at java.net.URLClassLoader.findClass(URLClassLoader.java:354) >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:425) >>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358) >>> ... 2 more >>> >>> >>> We did check that the table was there, so this is a bit puzzling. >>> >>> Thanks, >>> >>> Peter >>> >> >> > > > -- > Gaurav Kanade, > Software Engineer > Big Data > Cloud and Enterprise Division > Microsoft > -- Gaurav Kanade, Software Engineer Big Data Cloud and Enterprise Division Microsoft
