Member since
04-05-2016
188
Posts
19
Kudos Received
11
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
913 | 10-30-2017 07:05 AM | |
1196 | 10-12-2017 07:03 AM | |
4859 | 10-12-2017 06:59 AM | |
7124 | 03-01-2017 09:56 AM | |
21297 | 01-26-2017 11:52 AM |
02-22-2017
06:17 AM
@Sindhu I used a clean database for the hive metastore and i still get the same error message (below). hive_dev is the user. @Benjamin Leonhardi @Sunile Manjee @Kuldeep Kulkarni resource_management.core.exceptions.Fail: Execution of 'export HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ; /usr/hdp/current/hive-metastore/bin/schematool -initSchema -dbType mysql -userName hive_dev -passWord [PROTECTED]' returned 1. WARNING: Use "yarn jar" to launch YARN applications.
Metastore connection URL: jdbc:mysql://host/hive?createDatabaseIfNotExist=true
Metastore Connection Driver : com.mysql.jdbc.Driver
Metastore connection User: hive_dev
Starting metastore schema initialization to 1.2.1000
Initialization script hive-schema-1.2.1000.mysql.sql
Error: Specified key was too long; max key length is 1000 bytes (state=42000,code=1071)
org.apache.hadoop.hive.metastore.HiveMetaException: Schema initialization FAILED! Metastore state would be inconsistent !!
*** schemaTool failed ***
... View more
02-21-2017
07:05 AM
The error message from ambari while installing below... resource_management.core.exceptions.Fail: Execution of 'export HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ; /usr/hdp/current/hive-metastore/bin/schematool -initSchema -dbType mysql -userName hive_dev -passWord [PROTECTED]' returned 1. WARNING: Use "yarn jar" to launch YARN applications.
Metastore connection URL: jdbc:mysql://host/hivedb?createDatabaseIfNotExist=true
Metastore Connection Driver : com.mysql.jdbc.Driver
Metastore connection User: hive_dev
Starting metastore schema initialization to 1.2.1000
Initialization script hive-schema-1.2.1000.mysql.sql
Error: Specified key was too long; max key length is 1000 bytes (state=42000,code=1071)
org.apache.hadoop.hive.metastore.HiveMetaException: Schema initialization FAILED! Metastore state would be inconsistent !!
*** schemaTool failed ***
... View more
02-21-2017
06:54 AM
@Sindhu
Thanks. I recreated the hive DB when i reinstalled. see the output of the commands below; bin/schematool -initSchema -dbType mysql -dryRun
WARNING: Use "yarn jar" to launch YARN applications.
Metastore connection URL: jdbc:mysql://host/hivedb?createDatabaseIfNotExist=true
Metastore Connection Driver : com.mysql.jdbc.Driver
Metastore connection User: hive_dev
org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema version.
*** schemaTool failed ***
==================================================================================
output of select * from "VERSION"; on Hive metastore
mysql> select * from VERSION;
ERROR 1146 (42S02): Table 'hivedb.VERSION' doesn't exist
... View more
02-21-2017
06:04 AM
Hi, I am trying to reinstall Hive because i have issue with the metastore. I don't have an ibdata file anymore. I have run the schema tool but i still get the error below. I use mysql on HDP 2.4.3. bin/schematool -initSchema -dbType mysql
WARNING: Use "yarn jar" to launch YARN applications.
Metastore connection URL: jdbc:mysql://host/hivedb?createDatabaseIfNotExist=true
Metastore Connection Driver : com.mysql.jdbc.Driver
Metastore connection User: hive_dev
org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema version.
*** schemaTool failed ***
... View more
Labels:
01-31-2017
11:23 AM
@Matt Just got the error "An unexpected error has occurred. Action was performed, but no nodes are connected." while working with a flow. The flow simply takes log files and put in HDFS. NiFi went dead at the point of putting the files in HDFS. The file sizes are less than 150MB and there are only 24 of them. I have restarted the cluster and it's back up... 2017-01-31 12:01:42,731 ERROR [Leader Election Notification Thread-4] o.a.c.f.recipes.leader.LeaderSelector The leader threw an exception
java.lang.InterruptedException: null
at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326) ~[na:1.8.0_77]
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) ~[na:1.8.0_77]
at org.apache.curator.CuratorZookeeperClient.internalBlockUntilConnectedOrTimedOut(CuratorZookeeperClient.java:325) ~[curator-client-2.11.0.jar:na]
at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:106) ~[curator-client-2.11.0.jar:na]
at org.apache.curator.framework.imps.DeleteBuilderImpl.pathInForeground(DeleteBuilderImpl.java:240) ~[curator-framework-2.11.0.jar:na]
at org.apache.curator.framework.imps.DeleteBuilderImpl.forPath(DeleteBuilderImpl.java:225) ~[curator-framework-2.11.0.jar:na]
at org.apache.curator.framework.imps.DeleteBuilderImpl.forPath(DeleteBuilderImpl.java:35) ~[curator-framework-2.11.0.jar:na]
at org.apache.curator.framework.recipes.locks.LockInternals.deleteOurPath(LockInternals.java:339) ~[curator-recipes-2.11.0.jar:na]
at org.apache.curator.framework.recipes.locks.LockInternals.releaseLock(LockInternals.java:123) ~[curator-recipes-2.11.0.jar:na]
at org.apache.curator.framework.recipes.locks.InterProcessMutex.release(InterProcessMutex.java:154) ~[curator-recipes-2.11.0.jar:na]
at org.apache.curator.framework.recipes.leader.LeaderSelector.doWork(LeaderSelector.java:425) [curator-recipes-2.11.0.jar:na]
at org.apache.curator.framework.recipes.leader.LeaderSelector.doWorkLoop(LeaderSelector.java:441) [curator-recipes-2.11.0.jar:na]
at org.apache.curator.framework.recipes.leader.LeaderSelector.access$100(LeaderSelector.java:64) [curator-recipes-2.11.0.jar:na]
at org.apache.curator.framework.recipes.leader.LeaderSelector$2.call(LeaderSelector.java:245) [curator-recipes-2.11.0.jar:na]
at org.apache.curator.framework.recipes.leader.LeaderSelector$2.call(LeaderSelector.java:239) [curator-recipes-2.11.0.jar:na]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_77]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_77]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_77]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_77]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_77]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_77]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_77]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_77]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_77]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
... View more
01-31-2017
09:05 AM
thanks @Matt The NiFi cluster is a single node and it has the parameters nifi.cluster.flow.election.max.candidates=1 and nifi.cluster.flow.election.max.wait.time=5mins. However, my issue is the time it takes for the election...we have had to wait a whole weekend and these days it only works after a full restart. Is there any other way to speed up the election process?
... View more
01-30-2017
08:58 AM
1 Kudo
Hi, i have been experiencing some issues with my NiFi standalone. It starts with errors relating to leader election and of recent it just throws me out of the system completely. see the error message below;
... View more
Labels:
- Labels:
-
Apache NiFi
01-26-2017
11:52 AM
The issue was that some files with zero file size were causing the error. The zero-sized files were moved out and issue was resolved.
... View more
01-26-2017
09:54 AM
I am running an Hive query (my execution engine is Tez) on an external table with gz files. The error message i get is "java.io.EOFException: Unexpected end of input stream". I have done a check on HDFS for corrupt files and it returns a healthy status. Anyone come across a similar issue? Caused by: java.io.EOFException: Unexpected end of input streamat org.apache.hadoop.io.compress.DecompressorStream.decompress(DecompressorStream.java:145)at org.apache.hadoop.io.compress.DecompressorStream.read(DecompressorStream.java:85)at java.io.InputStream.read(InputStream.java:101)at org.apache.hadoop.util.LineReader.fillBuffer(LineReader.java:180)at org.apache.hadoop.util.LineReader.readDefaultLine(LineReader.java:216)at org.apache.hadoop.util.LineReader.readLine(LineReader.java:174)at org.apache.hadoop.mapred.LineRecordReader.skipUtfByteOrderMark(LineRecordReader.java:208)at org.apache.hadoop.mapred.LineRecordReader.next(LineRecordReader.java:246)at org.apache.hadoop.mapred.LineRecordReader.next(LineRecordReader.java:48)at org.apache.hadoop.hive.ql.io.HiveContextAwareRecordReader.doNext(HiveContextAwareRecordReader.java:350)... 22 more
Vertex did not succeed due to OWN_TASK_FAILURE, failedTasks:1 killedTasks:90, Vertex vertex_1483105407610_10086_1_00
... View more
Labels:
- Labels:
-
Apache Tez
01-26-2017
08:42 AM
Issue resolved! It was due to an account lock that was only discovered when i disconnected and tried reconnecting with SQL developer. Account has been unlocked and all good!
... View more