If you are facing issue Clock offset issue then there will be problem with your ntp is not in sync.   To resolve follow some commands   Check in which host it is giving problem go under that host through CLI and   1. systemctl status ntpd.service (For checking the status, if its not working the it showing Inactive message)   2. route -n copy the ntp server ip address (You will find under Destination column)    3. ntpdate <ntp server ip address>   4. systemctl start ntpd.service (for starting & syncing your host, after firing wait for sometime)   5. ntpstat (for checking whether it is synchronized or not it should be in synchronized)   after performing above steps your Clock offset issue will get resolved.   Regard,   ... View more

Done keyword is missing in your script. In your loop body use done at last. ... View more

thank you for your reply ... View more

check the status of hue server  ... View more

I am also having the same problem after I created directory and move the jar to the plugin folder: Here is the details:   You can see I have the .jar file in the right lib folder:       My environment variables are:   export FLUME_HOME=/opt/flume export FLUME_CONF_DIR=$FLUME_HOME/conf export FLUME_CLASSPATH=$FLUME_HOME_DIR export PATH=$FLUME_HOME/bin:$PATH and I am doing this under root user, below is the error message:   16/06/28 10:48:21 ERROR node.PollingPropertiesFileConfigurationProvider: Failed to load configuration data. Exception follows. org.apache.flume.FlumeException: Unable to load source type: com.cloudera.flume.source.TwitterSource, class: com.cloudera.flume.source.TwitterSource at org.apache.flume.source.DefaultSourceFactory.getClass(DefaultSourceFactory.java:67) at org.apache.flume.source.DefaultSourceFactory.create(DefaultSourceFactory.java:40) at org.apache.flume.node.AbstractConfigurationProvider.loadSources(AbstractConfigurationProvider.java:327) at org.apache.flume.node.AbstractConfigurationProvider.getConfiguration(AbstractConfigurationProvider.java:102) at org.apache.flume.node.PollingPropertiesFileConfigurationProvider$FileWatcherRunnable.run(PollingPropertiesFileConfigurationProvider.java:140) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.ClassNotFoundException: com.cloudera.flume.source.TwitterSource at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.apache.flume.source.DefaultSourceFactory.getClass(DefaultSourceFactory.java:65)   Can anyone shed any light on this with me? Thank you very much. ... View more

intermediate_access_logs was created as part of the ETL process in the tutorial. That process is done via Hive because it uses Hive SerDe's and other Hive-only features. The final table created in that process (tokenized_access_logs, if I remember correctly) is the one you should be able to query in Impala. Also, don't forget to 'invalidate metadata' when the ETL process is finished, since Impala doesn't cache metadata. ... View more