You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Amol <am...@gmail.com> on 2017/11/23 13:27:29 UTC
Unable to start Hadoop Accelerator with Persistence
I have installed apache-ignite-hadoop-2.3.0-bin on CDH and able start it
successfully.
But when I try to enable persistence providing the config file, it fails.
and below is the log. Can I know how it can be corrected.
[root@hdfc01gw01 ~]# echo $IGNITE_HOME
/applocaldata/ce_project/apache_ignite/apache-ignite-hadoop-2.3.0-bin
[ad_aagaiton@hdfc01gw01 ~]$ sudo su -
[root@hdfc01gw01 ~]# $IGNITE_HOME/bin/ignite.sh
/applocaldata/ce_project/apache_ignite/apache-ignite-fabric-2.3.0-bin/examples/config/persistentstore/example-persistent-store.xml
[05:15:47] __________ ________________
[05:15:47] / _/ ___/ |/ / _/_ __/ __/
[05:15:47] _/ // (7 7 // / / / / _/
[05:15:47] /___/\___/_/|_/___/ /_/ /___/
[05:15:47]
[05:15:47] ver. 2.3.0#20171027-sha1:8add7fd5
[05:15:47] 2017 Copyright(C) Apache Software Foundation
[05:15:47]
[05:15:47] Ignite documentation: http://ignite.apache.org
[05:15:47]
[05:15:47] Quiet mode.
[05:15:47] ^-- Logging to file
'/applocaldata/ce_project/apache_ignite/apache-ignite-hadoop-2.3.0-bin/work/log/ignite-e570a3f7.log'
[05:15:47] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
or "-v" to ignite.{sh|bat}
[05:15:47]
[05:15:47] OS: Linux 2.6.32-504.3.3.el6.x86_64 amd64
[05:15:47] VM information: Java(TM) SE Runtime Environment 1.7.0_67-b01
Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 24.65-b04
[05:15:47] Configured plugins:
[05:15:47] ^-- None
[05:15:47]
[05:15:47] Message queue limit is set to 0 which may lead to potential OOMEs
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
message queues growth on sender and receiver sides.
[05:15:47] Security status [authentication=off, tls/ssl=off]
[05:15:48] HADOOP_HOME is set to
/opt/cloudera/parcels/CDH-5.4.9-1.cdh5.4.9.p1230.998/lib/hadoop
[05:15:48] Resolved Hadoop classpath locations:
/opt/cloudera/parcels/CDH-5.4.9-1.cdh5.4.9.p1230.998/lib/hadoop,
/opt/cloudera/parcels/CDH-5.4.9-1.cdh5.4.9.p1230.998/lib/hadoop-hdfs,
/opt/cloudera/parcels/CDH-5.4.9-1.cdh5.4.9.p1230.998/lib/hadoop-mapreduce
[2017-11-23 05:15:49,518][ERROR][main][IgniteKernal] Got exception while
starting (will rollback startup routine).
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.jobMetaCache(HadoopJobTracker.java:206)
at
org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.onKernalStart(HadoopJobTracker.java:239)
at
org.apache.ignite.internal.processors.hadoop.HadoopProcessor.onKernalStart(HadoopProcessor.java:105)
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1060)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1909)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1652)
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1080)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:998)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:884)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
[05:15:49] Ignite node stopped OK [uptime=00:00:03.151]
class org.apache.ignite.IgniteException: null
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
at org.apache.ignite.Ignition.start(Ignition.java:350)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: null
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1110)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1909)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1652)
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1080)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:998)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:884)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
at org.apache.ignite.Ignition.start(Ignition.java:347)
... 1 more
Caused by: java.lang.NullPointerException
at
org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.jobMetaCache(HadoopJobTracker.java:206)
at
org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.onKernalStart(HadoopJobTracker.java:239)
at
org.apache.ignite.internal.processors.hadoop.HadoopProcessor.onKernalStart(HadoopProcessor.java:105)
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1060)
... 10 more
Failed to start grid: null
[root@hdfc01gw01 ~]#
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Unable to start Hadoop Accelerator with Persistence
Posted by Denis Mekhanikov <dm...@gmail.com>.
I don't see much sense in using both HDFS and Ignite native persistence,
since HDFS stores data on disk on its own.
Could you describe your use-case?
Maybe, there is a point to allow it, if there is a valid usage scenario.
Denis
сб, 25 нояб. 2017 г. в 6:31, Amol <am...@gmail.com>:
> Thanks for quick reply. Any reasons they have disabled for having native
> persistence with Hadoop?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: Unable to start Hadoop Accelerator with Persistence
Posted by Amol <am...@gmail.com>.
Thanks for quick reply. Any reasons they have disabled for having native
persistence with Hadoop?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Unable to start Hadoop Accelerator with Persistence
Posted by Denis Magda <dm...@apache.org>.
Alex,
Totally agree with you that even if the use case is meaningless the platform has to show a meaningful exception.
Don’t hesitate reporting usability issues like this immediately going forward:
https://issues.apache.org/jira/browse/IGNITE-7009 <https://issues.apache.org/jira/browse/IGNITE-7009>
—
Denis
> On Nov 23, 2017, at 3:00 PM, Alexey Kukushkin <ku...@gmail.com> wrote:
>
> Hi,
>
> I had same issue when I played with Hadoop a month ago. Developers told me it did not make sense having both Hadoop and native persistence :) However I still think we have at least a usability issue here since the exception does not tell much. Please let me know if you really need both persistence and Hadoop enabled. Otherwise I will open a usability issue to just request displaying a meaningful message for such a case.
Re: Unable to start Hadoop Accelerator with Persistence
Posted by Denis Magda <dm...@apache.org>.
Alex,
Totally agree with you that even if the use case is meaningless the platform has to show a meaningful exception.
Don’t hesitate reporting usability issues like this immediately going forward:
https://issues.apache.org/jira/browse/IGNITE-7009 <https://issues.apache.org/jira/browse/IGNITE-7009>
—
Denis
> On Nov 23, 2017, at 3:00 PM, Alexey Kukushkin <ku...@gmail.com> wrote:
>
> Hi,
>
> I had same issue when I played with Hadoop a month ago. Developers told me it did not make sense having both Hadoop and native persistence :) However I still think we have at least a usability issue here since the exception does not tell much. Please let me know if you really need both persistence and Hadoop enabled. Otherwise I will open a usability issue to just request displaying a meaningful message for such a case.
Re: Unable to start Hadoop Accelerator with Persistence
Posted by Alexey Kukushkin <ku...@gmail.com>.
Hi,
I had same issue when I played with Hadoop a month ago. Developers told me
it did not make sense having both Hadoop and native persistence :) However
I still think we have at least a usability issue here since the exception
does not tell much. Please let me know if you really need both persistence
and Hadoop enabled. Otherwise I will open a usability issue to just request
displaying a meaningful message for such a case.