Skip to main content



Spark Streaming Kafka Errors

 

We observed couple of errors / info messages while running Spark Streaming Applications, which might come  handy for debugging in future. Refer below - 

1) We noticed that Spark streaming Job was running but consuming nothing. We could see following messages being iteratively printed in logs - 


22/11/18 08:13:53 INFO AbstractCoordinator: [Consumer clientId=consumer-1, groupId=difnrt-uat-001] Group coordinator mymachine.com:9093 (id: 601150796 rack: null) is unavailable or invalid, will attempt rediscovery

22/11/18 08:13:53 INFO AbstractCoordinator: [Consumer clientId=consumer-1, groupId=difnrt-uat-001] Discovered group coordinator mymachine.com:9093 (id: 601150796 rack: null)

22/11/18 08:13:53 INFO AbstractCoordinator: [Consumer clientId=consumer-1, groupId=difnrt-uat-001] (Re-)joining group


Possible Causes / Fixes - 

  • May be due to Kafka Coordinator service. Try restarting Kafka it may fix the issue. 
  • In our case, we couldn't get help from Admin Team. So, we changed "group.id" which resolved issue for us.

2) Noticed Spark Streaming Job giving below error while producing messages to Kafka - 


org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 60000 ms.


Possible Causes / Fixes - 
  • It means that Client thread is being timed out before data is being written to Bootstrap server. There can be more reasons which can actually be derived from Kafka Server logs. Client logs don't provide much information.
  • In our case, it was firewall issue with some nodes in cluster which could not connect to Kafka Bootstrap servers. So, it used to work but when tasks used to execute on machine which doesn't have firewall open - that's when application used to fail. To identify it - 
    • we did SSH to those nodes 
    • executed below command's to know if connection is possible -
                    telnet <machine> <port> 
                    or,
                    nc -zv <machine> <port>

  • Opening firewall ports helped solve this intermittent problem. 

3) Spark Streaming with Kafka failing with below error -

java.lang.IllegalArgumentException: requirement failed: numRecords must not be negative
at scala.Predef$.require(Predef.scala:224)
at org.apache.spark.streaming.scheduler.StreamInputInfo.<init>(InputInfoTracker.scala:38)
at org.apache.spark.streaming.kafka010.DirectKafkaInputDStream.compute(DirectKafkaInputDStream.scala:231)

Possible Causes / Fixes - 
  • The reason for this error is that we are trying to fetch an offset which is greater then the current latest offset known by the broker. There can be multiple reasons for this behavior - 
  • On Kafka Side - 
    • set clean.leader.election.enable to false, such that there are no in-sync replicas.
    • Restart Kafka after there are no in-sync replicas.
    • Now, if offset was maintained by Kafka it should get corrected and re-running Spark Streaming application should work.
  • In my case - it was due to coding error - 
    • We were maintaining offset manually in an HBase Table. 
    • Due to a coding error - we inserted wrong value in HBase Table. 
    • Next time when our Job ran it selected large offset from HBase Table which did not exists for the topic resulting in this error.
    • We corrected our code and offset entries which resolved the issue.

Comments

Post a Comment

Popular posts

Spring MongoDB Rename field with derived Value of another field

Input Collection -  [ { 'k' : 'Troubleshooting' , 'hour' : '2024-10-10T16' , 'v' : [ 'WebPage, Login' ] }, { 'k' : 'TroubleshootingMe' , 'hour' : '2024-10-07T01' , 'v' : [ 'Accounts, etc' ] }  ] Expected Output -  [ { 'hour' : '2024-10-10T16' , 'Troubleshooting' : [ 'WebPage, Login' ] }, { 'hour' : '2024-10-07T01' , 'TroubleshootingMe' : [ 'Accounts, etc' ] }  ]   Above Can be achieved by  $replaceRoot / $replaceWith as follows - { $replaceWith : { $mergeObjects : [ { hour : "$hour" }, { "$arrayToObject" : [ [ { k : "$k" , v : "$v" } ] ] } ] } } or { $replaceRoo...
Post a Comment
Read more




What is Leadership

 
Post a Comment
Read more




Spark Error - missing part 0 of the schema, 2 parts are expected

 Exception -  Caused by: org.apache.spark.sql.AnalysisException : Could not read schema from the hive metastore because it is corrupted. (missing part 0 of the schema, 2 parts are expected).; Analysis -  ·          Check for table definition. In TBLProperties, you might find something like this – > spark.sql.sources.schema.numPartCols > 'spark.sql.sources.schema.numParts' 'spark.sql.sources.schema.part.0' > 'spark.sql.sources.schema.part.1' 'spark.sql.sources.schema.part.2' > 'spark.sql.sources.schema.partCol.0' > 'spark.sql.sources.schema.partCol.1' That’s what error seems to say that part1 is defined but part0 is missing.  Solution -  Drop & re-create table. If Table was partitioned  then all partitions  would have been removed. So do either of below -  ·          Msck repair table <db_name>.<table_name> ·    ...
Post a Comment
Read more




Spark MongoDB Connector Not leading to correct count or data while reading

  We are using Scala 2.11 , Spark 2.4 and Spark MongoDB Connector 2.4.4 Use Case 1 - We wanted to read a Shareded Mongo Collection and copy its data to another Mongo Collection. We noticed that after Spark Job successful completion. Output MongoDB did not had many records. Use Case 2 -  We read a MongoDB collection and doing count on dataframe lead to different count on each execution. Analysis,  We realized that MongoDB Spark Connector is missing data on bulk read as a dataframe. We tried various partitioner, listed on page -  https://www.mongodb.com/docs/spark-connector/v2.4/configuration/  But, none of them worked for us. Finally, we tried  MongoShardedPartitioner  this lead to constant count on each execution. But, it was greater than the actual count of records on the collection. This seems to be limitation with MongoDB Spark Connector. But,  MongoShardedPartitioner  seemed closest possible solution to this kind of situation. But, it per...
Post a Comment
Read more




Read from a hive table and write back to it using spark sql

In context to Spark 2.2 - if we read from an hive table and write to same, we get following exception- scala > dy . write . mode ( "overwrite" ). insertInto ( "incremental.test2" ) org . apache . spark . sql . AnalysisException : Cannot insert overwrite into table that is also being read from .; org . apache . spark . sql . AnalysisException : Cannot insert overwrite into table that is also being read from .; 1. This error means that our process is reading from same table and writing to same table. 2. Normally, this should work as process writes to directory .hiveStaging... 3. This error occurs in case of saveAsTable method, as it overwrites entire table instead of individual partitions. 4. This error should not occur with insertInto method, as it overwrites partitions not the table. 5. A reason why this happening is because Hive table has following Spark TBLProperties in its definition. This problem will solve for insertInto met...
Post a Comment
Read more