question Re: IllegalArgumentException and Illegal partition for 'val' in sqoop in Support Questions

IllegalArgumentException and Illegal partition for 'val' in sqoop

sim6 — Fri, 16 Sep 2022 10:28:28 GMT

I have asked this question over and over and am starting to believe that I am missing out on something really basic here. Not a lot of people seem to have come across this and I am really stuck on this one:

I get this error when I specify merge key argument with incremental import lastmodified in sqoop. If I run the job through command line, it works alright but not when I submit it to oozie. I submit my jobs through oozie. Not sure if oozie is the problem or hue, but sqoop job is not since it really works fine when executed through command line including the merge step.

My sqoop job looks like this:

sqoop job --meta-connect jdbc:hsqldb:hsql://FQDN:16000/sqoop 
--create test_table -- import --driver com.mysql.jdbc.Driver --connect
jdbc:mysql://IP/DB?zeroDateTimeBehavior=convertToNull --username 
USER_NAME --password 'PASSWORD' --table test_table --merge-key id --
split-by id --target-dir LOCATION --incremental lastmodified 
--last-value 0 --check-column updated_at

The first import works alright .Starting second import I get:

I created a small test table to test with an int, datetime and varchar , without any NULL or invalid chars in the data and yet I faced the same issue:

# id, updated_at, name
'1', '2016-07-02 17:16:53', 'l'
'3', '2016-06-29 14:12:53', 'f'

There were only 2 rows in the data and yet I got this:

Error: java.lang.IllegalArgumentException
at java.nio.ByteBuffer.allocate(ByteBuffer.java:330)
at org.apache.hadoop.mapred.SpillRecord.<init>(SpillRecord.java:51)
at org.apache.hadoop.mapred.MapTask$MapOutputBuffer.mergeParts(MapTask.java:1848)
at org.apache.hadoop.mapred.MapTask$MapOutputBuffer.flush(MapTask.java:1508)
at org.apache.hadoop.mapred.MapTask$NewOutputCollector.close(MapTask.java:723)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:793)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1693)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)

Error: java.io.IOException: Illegal partition for 3 (-2)
at org.apache.hadoop.mapred.MapTask$MapOutputBuffer.collect(MapTask.java:1083)
at org.apache.hadoop.mapred.MapTask$NewOutputCollector.write(MapTask.java:715)
at org.apache.hadoop.mapreduce.task.TaskInputOutputContextImpl.write(TaskInputOutputContextImpl.java:89)
at org.apache.hadoop.mapreduce.lib.map.WrappedMapper$Context.write(WrappedMapper.java:112)
at org.apache.sqoop.mapreduce.MergeMapperBase.processRecord(MergeMapperBase.java:82)
at org.apache.sqoop.mapreduce.MergeTextMapper.map(MergeTextMapper.java:58)
at org.apache.sqoop.mapreduce.MergeTextMapper.map(MergeTextMapper.java:34)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:145)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:787)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1693)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)

Error: java.lang.IllegalArgumentException
at java.nio.ByteBuffer.allocate(ByteBuffer.java:330)
at org.apache.hadoop.mapred.SpillRecord.<init>(SpillRecord.java:51)
at org.apache.hadoop.mapred.MapTask$MapOutputBuffer.mergeParts(MapTask.java:1848)
at org.apache.hadoop.mapred.MapTask$MapOutputBuffer.flush(MapTask.java:1508)
at org.apache.hadoop.mapred.MapTask$NewOutputCollector.close(MapTask.java:723)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:793)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1693)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)

Error: java.io.IOException: Illegal partition for 1 (-2)
at org.apache.hadoop.mapred.MapTask$MapOutputBuffer.collect(MapTask.java:1083)
at org.apache.hadoop.mapred.MapTask$NewOutputCollector.write(MapTask.java:715)
at org.apache.hadoop.mapreduce.task.TaskInputOutputContextImpl.write(TaskInputOutputContextImpl.java:89)
at org.apache.hadoop.mapreduce.lib.map.WrappedMapper$Context.write(WrappedMapper.java:112)
at org.apache.sqoop.mapreduce.MergeMapperBase.processRecord(MergeMapperBase.java:82)
at org.apache.sqoop.mapreduce.MergeTextMapper.map(MergeTextMapper.java:58)
at org.apache.sqoop.mapreduce.MergeTextMapper.map(MergeTextMapper.java:34)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:145)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:787)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1693)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)

I get this error only in OOZIE and submit the job through HUE and this works just fine including the Merge mapreduce when I run the sqoop job through command line

Taken from oozie launcher, This is what my mapreduce job logs look like:

>>> Invoking Sqoop command line now >>>
5373 [uber-SubtaskRunner] WARN org.apache.sqoop.tool.SqoopTool - $SQOOP_CONF_DIR has not been set in the environment. Cannot check for additional configuration.
5407 [uber-SubtaskRunner] INFO org.apache.sqoop.Sqoop - Running Sqoop version: 1.4.6-cdh5.7.0
5702 [uber-SubtaskRunner] WARN org.apache.sqoop.tool.BaseSqoopTool - Setting your password on the command-line is insecure. Consider using -P instead.
5715 [uber-SubtaskRunner] WARN org.apache.sqoop.ConnFactory - $SQOOP_CONF_DIR has not been set in the environment. Cannot check for additional configuration.
5740 [uber-SubtaskRunner] WARN org.apache.sqoop.ConnFactory - Parameter --driver is set to an explicit driver however appropriate connection manager is not being set (via --connection-manager). Sqoop is going to fall back to org.apache.sqoop.manager.GenericJdbcManager. Please specify explicitly which connection manager should be used next time.
5754 [uber-SubtaskRunner] INFO org.apache.sqoop.manager.SqlManager - Using default fetchSize of 1000
5754 [uber-SubtaskRunner] INFO org.apache.sqoop.tool.CodeGenTool - Beginning code generation
6091 [uber-SubtaskRunner] INFO org.apache.sqoop.manager.SqlManager - Executing SQL statement: SELECT t.* FROM test_table AS t WHERE 1=0
6098 [uber-SubtaskRunner] INFO org.apache.sqoop.manager.SqlManager - Executing SQL statement: SELECT t.* FROM test_table AS t WHERE 1=0
6118 [uber-SubtaskRunner] INFO org.apache.sqoop.orm.CompilationManager - HADOOP_MAPRED_HOME is /opt/cloudera/parcels/CDH-5.7.0-1.cdh5.7.0.p0.45/lib/hadoop-mapreduce
8173 [uber-SubtaskRunner] INFO org.apache.sqoop.orm.CompilationManager - Writing jar file: /tmp/sqoop-yarn/compile/454902ac78d49b783a1f51b7bfe0a2be/test_table.jar
8185 [uber-SubtaskRunner] INFO org.apache.sqoop.manager.SqlManager - Executing SQL statement: SELECT t.* FROM test_table AS t WHERE 1=0
8192 [uber-SubtaskRunner] INFO org.apache.sqoop.tool.ImportTool - Incremental import based on column updated_at
8192 [uber-SubtaskRunner] INFO org.apache.sqoop.tool.ImportTool - Lower bound value: '2016-07-02 17:13:24.0'
8192 [uber-SubtaskRunner] INFO org.apache.sqoop.tool.ImportTool - Upper bound value: '2016-07-02 17:16:56.0'
8194 [uber-SubtaskRunner] INFO org.apache.sqoop.mapreduce.ImportJobBase - Beginning import of test_table
8214 [uber-SubtaskRunner] INFO org.apache.sqoop.manager.SqlManager - Executing SQL statement: SELECT t.* FROM test_table AS t WHERE 1=0
8230 [uber-SubtaskRunner] WARN org.apache.sqoop.mapreduce.JobBase - SQOOP_HOME is unset. May not be able to find all job dependencies.
8716 [uber-SubtaskRunner] INFO org.apache.sqoop.mapreduce.db.DBInputFormat - Using read commited transaction isolation
8717 [uber-SubtaskRunner] INFO org.apache.sqoop.mapreduce.db.DataDrivenDBInputFormat - BoundingValsQuery: SELECT MIN(id), MAX(id) FROM test_table WHERE ( updated_at >= '2016-07-02 17:13:24.0' AND updated_at < '2016-07-02 17:16:56.0' )
8721 [uber-SubtaskRunner] INFO org.apache.sqoop.mapreduce.db.IntegerSplitter - Split size: 0; Num splits: 4 from: 1 to: 1
25461 [uber-SubtaskRunner] INFO org.apache.sqoop.mapreduce.ImportJobBase - Transferred 26 bytes in 17.2192 seconds (1.5099 bytes/sec)
25471 [uber-SubtaskRunner] INFO org.apache.sqoop.mapreduce.ImportJobBase - Retrieved 1 records.
25536 [uber-SubtaskRunner] WARN org.apache.sqoop.mapreduce.ExportJobBase - IOException checking input file header: java.io.EOFException
25550 [uber-SubtaskRunner] WARN org.apache.sqoop.mapreduce.JobBase - SQOOP_HOME is unset. May not be able to find all job dependencies.
Heart beat
Heart beat
70628 [uber-SubtaskRunner] ERROR org.apache.sqoop.tool.ImportTool - Merge MapReduce job failed!
70628 [uber-SubtaskRunner] INFO org.apache.sqoop.tool.ImportTool - Saving incremental import state to the metastore
70831 [uber-SubtaskRunner] INFO org.apache.sqoop.tool.ImportTool - Updated data for job: test_table

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

yshi — Mon, 04 Jul 2016 02:26:37 GMT

Hi sim6,

Thanks for reporting this problem!

This problem is weird. The first thing I have noticed is that we are using Uber mode with Oozie Launchers. Could you please try to disable it and see whether it helps? To do this, please set below in oozie-site.xml of Oozie Server:

<property>
<name>oozie.action.launcher.mapreduce.job.ubertask.enable</name>
<value>false</value>
</property>

If you are using Cloudera Manager, please set them in Oozie server safety valve and then restart Oozie server. If you are not using CM, please manually add it to oozie-site.xml and restart Oozie Server.

If you still have this problem after disabling Oozie Launcher uber mode, please try to collect the configuration of one failed and one succeeded Sqoop Merge job. The stack trace shows that the mapper output collector cannot write the data because it cannot find the partition for the given output key (1 and 3 for your data). I am suspecting that the partitioner passed to the jobs are different.

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

sim6 — Mon, 04 Jul 2016 05:33:11 GMT

Thanks. I feel a bit relaxed after hearing something on this.I am usign CM and I tried setting uber mode off. It still has the same problem. 😞 i haven't seen any of my merge jobs succeeding .I have tried it with different data from different databases as well but never did it work right. @yshi

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

yshi — Mon, 04 Jul 2016 07:39:03 GMT

This is really weird. Could you please upload the diagnostic data of one failed merge job together with one successful job?

To get the diagnostic data of a job, please go to CM > YARN > Applications, find the job, click the buttom to its right and choose "Collect Diagnostic Data". In the popout diaglogue, please confirm the operation and download the result data after it finishes.

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

sim6 — Mon, 04 Jul 2016 07:50:15 GMT

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

Markus Kemper — Mon, 04 Jul 2016 11:40:30 GMT

Hello Sim6,

My understanding (will confirm) is as follows:

The --merge-key option is part of the Sqoop1 merge command and not available to be used with the Sqoop1 import command
The Sqoop1 merge command is intented to run after (separate job) to flatten the two datasets that exist in HDFS as a result of multiple Sqoop1 import commands (commonly created with --incremental however not exclusively)

If you remove "--merge-key id" from your command, does it work without error?

Thank you,

Markus Kemper

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

sim6 — Mon, 04 Jul 2016 12:34:16 GMT

@Markus Kemper: That's right. But then we already have the file in target dir when running the import for second time. It throws error that either import using incremental append or specify merge key when target dir already exists and using incremental lastmodified.

Using sqoop merge command in a seprate job sounds okay but I would like to have --merge-key to work when it's available 😄 .

Also, the link https://community.hortonworks.com/questions/10710/sqoop-incremental-import-working-fine-now-i-want-k.html suggests to use --merge-key with import command only and has been confirmed that it works.

This link herehttp://stackoverflow.com/questions/34400973/apache-sqoop-incremental-import?rq=1 also confirms that it works

Also, it works when I run the sqoop job through CLI. It gives this problem only when running it through oozie

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

yshi — Mon, 04 Jul 2016 12:28:49 GMT

@Markus Kemper Although not documented, we can use "--merge-key" in Sqoop import command if "--incremental lastmodified" is used. If the target dir is not empty, the Sqoop import tool will automatically run a merge job after the import job is finished to merge the data. Please see below source code for details:

https://github.com/cloudera/sqoop/blob/cdh5-1.4.6_5.7.1/src/java/org/apache/sqoop/tool/ImportTool.java#L515-L517

https://github.com/cloudera/sqoop/blob/cdh5-1.4.6_5.7.1/src/java/org/apache/sqoop/tool/ImportTool.java#L432-L433

@sim6

I have just realized that you are express edition of Cloudera Manager. It may not have the function of collecting diagnostic data of jobs.

Please help manually check:
1) Please add parameter "--verbose" and "-Dmapreduce.map.log.level=DEUBG" to your Sqoop import command, run the sqoop job and. After it failed, please upload ALL the sqoop command output and the failed MR job logs (use command "yarn logs -applicationId=<app_id>" to get it)

2) The value of property "mapreduce.job.partitioner.class" in both successful and failed jobs

3) The value of property "sqoop.merge.key.col" in both successful and failed jobs

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

sim6 — Mon, 04 Jul 2016 12:56:02 GMT

To enable the logs, I added it to my job :

sqoop job -Dmapreduce.map.log.level=DEUBG --meta-connect jdbc:hsqldb:hsql://FQDN:16000/sqoop --verbose --create test_table -- import --driver com.mysql.jdbc.Driver --connect jdbc:mysql://ip3/testdb?zeroDateTimeBehavior=convertToNull --username root --password 'password' --table test_table --merge-key id --split-by id --target-dir location --incremental lastmodified --last-value 0 --check-column updated_at

But trying to get the logs, I still get:

/tmp/logs/root/logs/application_1463739226103_5116does not exist.

Log aggregation has not completed or is not enabled.

As a sidenote: I have also tried to change time zone of sqoop job in similar manner using -D option and that did not work either. Am I adding it in an incorrect way to the sqoop job? @yshi

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

Markus Kemper — Mon, 04 Jul 2016 12:57:32 GMT

@yshi,

re: Sqoop1 import + --incremental + --merge-key

Although not documented, we can use "--merge-key" in Sqoop import command if "--incremental lastmodified" is used. If the target dir is not empty, the Sqoop import tool will automatically run a merge job after the import job is finished to merge the data

Thank you for pointing this out, I will review further and create a Sqoop1 Doc Jira as necessary to properly address the command usage and expected behavior.

@sim6,

Let's follow @yshi's approach on debugging further for now while I review the documentation issue in the background.

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

yshi — Mon, 04 Jul 2016 13:14:50 GMT

@sim6

Could you please let me know under which user you submitted the oozie Sqoop job? Is it the same user as you ran the job on command line? If you are using different users for Oozie and command line jobs, please try to switch to the same user and see whether it brings any change.

As for the application logs, we may need to specify the application owner to be able to get it. Please try below command:

sudo -u mapred yarn logs -applicationId <app_id> -appOwner <owner>

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

sim6 — Mon, 04 Jul 2016 13:48:51 GMT

Thank you.

I do get the logs now but none of the jobs have the two properties you asked for, Shall I share rest of the properties from the logs ? @yshi

Also, from the command line, I execute the job with both root user and hue user and the execution succedes in both the cases without any problem. My job is submitted to oozie using hue user only and that one fails.

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

sim6 — Tue, 05 Jul 2016 04:58:04 GMT

@yshi: I did sqoop job --show test_table

I get the following results:

verbose = false
incremental.last.value = 2016-07-05 05:29:33.0
db.connect.string = jdbc:mysql://10.10.11.3/testdb?zeroDateTimeBehavior=convertToNull
codegen.output.delimiters.escape = 0
codegen.output.delimiters.enclose.required = false
codegen.input.delimiters.field = 0
split.limit = null
hbase.create.table = false
db.require.password = false
hdfs.append.dir = false
db.table = test_table
codegen.input.delimiters.escape = 0
db.password = St@N!$$r3789L0vE
accumulo.create.table = false
import.fetch.size = null
codegen.input.delimiters.enclose.required = false
db.username = root
reset.onemapper = false
codegen.output.delimiters.record = 10
import.max.inline.lob.size = 16777216
hbase.bulk.load.enabled = false
hcatalog.create.table = false
db.clear.staging.table = false
incremental.col = updated_at
codegen.input.delimiters.record = 0
enable.compression = false
hive.overwrite.table = false
hive.import = false
codegen.input.delimiters.enclose = 0
accumulo.batch.size = 10240000
hive.drop.delims = false
customtool.options.jsonmap = {}
codegen.output.delimiters.enclose = 0
hdfs.delete-target.dir = false
codegen.output.dir = .
codegen.auto.compile.dir = true
relaxed.isolation = false
mapreduce.num.mappers = 4
accumulo.max.latency = 5000
import.direct.split.size = 0
codegen.output.delimiters.field = 44
export.new.update = UpdateOnly
incremental.mode = DateLastModified
hdfs.file.format = TextFile
codegen.compile.dir = /tmp/sqoop-root/compile/58af2027880638f91ea875a1c51b5de8
direct.import = false
db.split.column = id
hdfs.target.dir = /user/hue/ERP/testinc
hive.fail.table.exists = false
merge.key.col = id
jdbc.driver.class = com.mysql.jdbc.Driver
db.batch = false

Value of merge.key.col as expected is id.

But I still do not get the value other attribute you asked for. @yshi

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

yshi — Tue, 05 Jul 2016 13:18:07 GMT

@sim6

Sorry for the late response! I am currently on a holiday, and thus can only check this problem occasionally.

It doesn't make sense that the merge job doesn't have a partitioner class, because it does need a reduce phase to merge the records. Could you please:

1) Make sure that you are checking the merge job, not the import job.

2) Please check the number of reducers of the failed merge job

3) Please try to add parameter "-Dmapred.reduce.tasks=1" to your Sqoop import job and see whether it helps

4) If nothing above helps, let's try to narrow down the problem a bit by removing the impact of Sqoop metastore. Please run the command directly in Oozie Sqoop action instead of storing it in metastore. The command should be something like below (I have removed the --driver parameter as well to use the MySQL connector instead of the generic JDBC connector, although it shouldn't make any difference for our problem).

sqoop import -Dmapred.reduce.tasks=1 --connect
jdbc:mysql://IP/DB?zeroDateTimeBehavior=convertToNull --username 
USER_NAME --password 'PASSWORD' --table test_table --merge-key id --
split-by id --target-dir LOCATION --incremental lastmodified 
--last-value 0 --check-column updated_at

When I have some time, I will try to reproduce your problem. Please let me know the CDH and CM version you are using.

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

sim6 — Wed, 06 Jul 2016 05:19:49 GMT

Awesome. Using

-Dmapred.reduce.tasks=1

worked. I used it in my job with --meta-connect arguement as well and it still works 🙂 I would really like to understand what goes behind the scenes. Could you please explain why exactly I needed to use this argument? @yshi

Also, I posted an issue here and it seems to not have gained any attention, Could you please have a look at it and let me know if this is supported at all?

http://community.cloudera.com/t5/Data-Ingestion-Integration/change-sqoop-metastore-timezone-to-GMT/m-p/42596/highlight/true#M1701

Other than that, Thank you for keeping up all this time and helping out 🙂 . Happy holiday 🙂 🙂

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

yshi — Thu, 07 Jul 2016 08:55:53 GMT

@sim6

I am not 100% sure how my solutions works at this moment. And because I am on holiday, I cannot reproduce this problem to figure out the exact root cause.

I worked out this workaround with below observations:

1) Sqoop import job has no reducers, but Sqoop merge job does have merge job

2) According to all the information you have provided, your Oozie Sqoop job seems to fail because lack of partition class definition in job configuration.

3) I was suspecting that Oozie Sqoop reuse the jobConf object between Sqoop import and merge job, and thus accidentally set the number of reducers in merge job to 0. By explicitly setting the number of reducers to 1, we might be able to workaround this problem. And we are lucky that this does work. 🙂

I will later try to reproduce this problem and check whether my theory is correct or not.

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

yshi — Mon, 11 Jul 2016 07:40:40 GMT

@sim6

I cannot reproduce your problem on my local cluster. Not sure how this happened to you.

Please remember to increase the number of reducers when your data grow. 1 reducer is definitely not enough for big tables.

I will have a look at the other problem you asked here when I have some time.

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

sim6 — Wed, 13 Jul 2016 18:31:21 GMT

Thank you. I see that but I have always had this issue and is likely to happen again on increasing the number of clusters.Could it be some configurations or something that are causing this particular issue?

Also, look forward to a response on the other question. Thank you 🙂 @yshi

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

sim6 — Tue, 19 Jul 2016 06:00:07 GMT

@yshi: Hey, was hoping to hear back on the other issue I had created 🙂 . Is there a way I can bump that question on the forum to get some attention to it?

Re: IllegalArgumentException and Illegal partition for 'val' in sqoop

yshi — Tue, 19 Jul 2016 07:07:49 GMT

@sim6

Sorry, I am very busy these days to catch up with my work after the holiday.

I will find some time to look at the other problem tomorrow.