You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Konstantin Boudnik <co...@apache.org> on 2017/06/07 20:40:45 UTC
Configuration issues with IGFS in Ignite 1.9
Guys,
after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing
a number of issues introduced by changed script interfaces and
similar. However, the one which I still can not fix so far is this.
The secondary file system is configured like this:
<property name="fileSystemConfiguration">
<list>
<bean class="org.apache.ignite.configuration.FileSystemConfiguration"
parent="igfsCfgBase">
<property name="name" value="igfs"/>
<!-- Caches with these names must be configured. -->
<property name="metaCacheName" value="igfs-meta"/>
<property name="dataCacheName" value="igfs-data"/>
<!-- Configure TCP endpoint for communication with the file
system instance. -->
<property name="ipcEndpointConfiguration">
<bean class="org.apache.ignite.igfs.IgfsIpcEndpointConfiguration">
<property name="type" value="TCP" />
<property name="host" value="0.0.0.0" />
<property name="port" value="10500" />
</bean>
</property>
<property name="secondaryFileSystem">
<bean
class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
<constructor-arg name="uri"
value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
<constructor-arg name="cfgPath"
value='/etc/hadoop/conf/core-site.xml'/>
<constructor-arg name="userName" value="ignite"/>
</bean>
</property>
And we are getting the following error message:
Caused by: java.lang.IllegalArgumentException: Can not create a Path
from an empty string
at org.apache.hadoop.fs.Path.checkPathArg(Path.java:126)
at org.apache.hadoop.fs.Path.<init>(Path.java:134)
at org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopBasicFileSystemFactoryDelegate.start(HadoopBasicFileSystemFactoryDelegate
.java:165)
at org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopCachingFileSystemFactoryDelegate.start(HadoopCachingFileSystemFactoryDele
gate.java:58)
at org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopIgfsSecondaryFileSystemDelegateImpl.start(HadoopIgfsSecondaryFileSystemDe
legateImpl.java:375)
at org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:261)
at org.apache.ignite.internal.processors.igfs.IgfsImpl.<init>(IgfsImpl.java:186)
at org.apache.ignite.internal.processors.igfs.IgfsContext.<init>(IgfsContext.java:101)
at org.apache.ignite.internal.processors.igfs.IgfsProcessor.start(IgfsProcessor.java:130)
at org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1644)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:903)
... 10 more
Failed to start grid: Can not create a Path from an empty string
Removing the value from cfgPath doesn't change anything. I'd
appreciate if someone can point me to the right direction: current
config examples aren't helping much either. Thanks!
--
Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.
Re: Configuration issues with IGFS in Ignite 1.9
Posted by Konstantin Boudnik <co...@apache.org>.
Sorry, please disregard the last one - that's my omission. service.sh
script is still fine!
--
Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.
On Fri, Jun 9, 2017 at 12:19 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Vladimir,
>
> one more issue - it seems that ignite script (bin/ignite.sh) doesn't
> respond to 'stop' command anymore as it was the case in the earlier
> versions of it. As the result, linux init scripts have no control over
> it rather than simply kill the process. Is it the intention or am I
> missing something?
>
> Thank you very much!
> Cos
>
> --
> Take care,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Fri, Jun 9, 2017 at 11:05 AM, Konstantin Boudnik <co...@apache.org> wrote:
>> Yey! That did the trick, thank you for your help! It'd be great to
>> have this fix for sure!
>> --
>> Take care,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>>
>> Disclaimer: Opinions expressed in this email are those of the author,
>> and do not necessarily represent the views of any company the author
>> might be affiliated with at the moment of writing.
>>
>>
>> On Fri, Jun 9, 2017 at 6:41 AM, Vladimir Ozerov <vo...@gridgain.com> wrote:
>>> Cos,
>>>
>>> This is a problem with our URI parsing. Please add a slash to the end and
>>> it should work: "hdfs://0f6e4ed13002.bigtop.apache.org:8020*/*". I'll
>>> create a ticket for this.
>>>
>>> On Thu, Jun 8, 2017 at 9:28 PM, Konstantin Boudnik <co...@apache.org> wrote:
>>>
>>>> Thank you for your help, Vladimir. Unfortunately, I am still seeing
>>>> the same behavior while attempting to bring up the service. The full
>>>> element's configuration could be found at [1]
>>>> Can we perhaps get on a skype/hangout for a few minutes so we can
>>>> resolve this quickly? Unless, I am doing something silly and missing
>>>> it, of course.
>>>>
>>>> That'd be a great help!
>>>>
>>>> [1] https://gist.github.com/c0s/cfb2b78a87f4f7f3ef4c1fa0bb5c4dea
>>>>
>>>> --
>>>> Take care,
>>>> Konstantin (Cos) Boudnik
>>>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>>>>
>>>> Disclaimer: Opinions expressed in this email are those of the author,
>>>> and do not necessarily represent the views of any company the author
>>>> might be affiliated with at the moment of writing.
>>>>
>>>>
>>>> On Thu, Jun 8, 2017 at 1:23 AM, Vladimir Ozerov <vo...@gridgain.com>
>>>> wrote:
>>>> > Hi Cos,
>>>> >
>>>> > Please try this one:
>>>> >
>>>> > <property name="secondaryFileSystem">
>>>> > <bean
>>>> > class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
>>>> > <property name="fileSystemFactory">
>>>> > <bean
>>>> > class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
>>>> > <property name="uri" value="hdfs://
>>>> > 0f6e4ed13002.bigtop.apache.org:8020"/>
>>>> > <property name="configPaths">
>>>> > <list>
>>>> > <value>/etc/hadoop/conf/core-site.xml</value>
>>>> > </list>
>>>> > </property>
>>>> > </bean>
>>>> > </property>
>>>> > <property name="defaultUserName" value="ignite" />
>>>> > </bean>
>>>> > </property>
>>>> >
>>>> > Vladimir.
>>>> >
>>>> > On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik <co...@apache.org>
>>>> wrote:
>>>> >
>>>> >> Guys,
>>>> >>
>>>> >> after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing
>>>> >> a number of issues introduced by changed script interfaces and
>>>> >> similar. However, the one which I still can not fix so far is this.
>>>> >> The secondary file system is configured like this:
>>>> >>
>>>> >> <property name="fileSystemConfiguration">
>>>> >> <list>
>>>> >> <bean class="org.apache.ignite.configuration.
>>>> >> FileSystemConfiguration"
>>>> >> parent="igfsCfgBase">
>>>> >> <property name="name" value="igfs"/>
>>>> >>
>>>> >> <!-- Caches with these names must be configured. -->
>>>> >> <property name="metaCacheName" value="igfs-meta"/>
>>>> >> <property name="dataCacheName" value="igfs-data"/>
>>>> >>
>>>> >> <!-- Configure TCP endpoint for communication with the file
>>>> >> system instance. -->
>>>> >> <property name="ipcEndpointConfiguration">
>>>> >> <bean class="org.apache.ignite.igfs.
>>>> >> IgfsIpcEndpointConfiguration">
>>>> >> <property name="type" value="TCP" />
>>>> >> <property name="host" value="0.0.0.0" />
>>>> >> <property name="port" value="10500" />
>>>> >> </bean>
>>>> >> </property>
>>>> >>
>>>> >> <property name="secondaryFileSystem">
>>>> >> <bean
>>>> >> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
>>>> ystem">
>>>> >> <constructor-arg name="uri"
>>>> >> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
>>>> >> <constructor-arg name="cfgPath"
>>>> >> value='/etc/hadoop/conf/core-site.xml'/>
>>>> >> <constructor-arg name="userName" value="ignite"/>
>>>> >> </bean>
>>>> >> </property>
>>>> >>
>>>> >> And we are getting the following error message:
>>>> >>
>>>> >> Caused by: java.lang.IllegalArgumentException: Can not create a Path
>>>> >> from an empty string
>>>> >> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:126)
>>>> >> at org.apache.hadoop.fs.Path.<init>(Path.java:134)
>>>> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>>>> >> HadoopBasicFileSystemFactoryDelegate.start(
>>>> HadoopBasicFileSystemFactoryDe
>>>> >> legate
>>>> >> .java:165)
>>>> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>>>> >> HadoopCachingFileSystemFactoryDelegate.start(
>>>> >> HadoopCachingFileSystemFactoryDele
>>>> >> gate.java:58)
>>>> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>>>> >> HadoopIgfsSecondaryFileSystemDelegateImpl.start(
>>>> >> HadoopIgfsSecondaryFileSystemDe
>>>> >> legateImpl.java:375)
>>>> >> at org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
>>>> >> ystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:261)
>>>> >> at org.apache.ignite.internal.processors.igfs.IgfsImpl.<
>>>> >> init>(IgfsImpl.java:186)
>>>> >> at org.apache.ignite.internal.processors.igfs.IgfsContext.<
>>>> >> init>(IgfsContext.java:101)
>>>> >> at org.apache.ignite.internal.processors.igfs.IgfsProcessor.
>>>> >> start(IgfsProcessor.java:130)
>>>> >> at org.apache.ignite.internal.IgniteKernal.startProcessor(
>>>> >> IgniteKernal.java:1644)
>>>> >> at org.apache.ignite.internal.IgniteKernal.start(
>>>> >> IgniteKernal.java:903)
>>>> >> ... 10 more
>>>> >> Failed to start grid: Can not create a Path from an empty string
>>>> >>
>>>> >> Removing the value from cfgPath doesn't change anything. I'd
>>>> >> appreciate if someone can point me to the right direction: current
>>>> >> config examples aren't helping much either. Thanks!
>>>> >> --
>>>> >> Take care,
>>>> >> Konstantin (Cos) Boudnik
>>>> >> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>>>> >>
>>>> >> Disclaimer: Opinions expressed in this email are those of the author,
>>>> >> and do not necessarily represent the views of any company the author
>>>> >> might be affiliated with at the moment of writing.
>>>> >>
>>>>
Re: Configuration issues with IGFS in Ignite 1.9
Posted by Konstantin Boudnik <co...@apache.org>.
Vladimir,
one more issue - it seems that ignite script (bin/ignite.sh) doesn't
respond to 'stop' command anymore as it was the case in the earlier
versions of it. As the result, linux init scripts have no control over
it rather than simply kill the process. Is it the intention or am I
missing something?
Thank you very much!
Cos
--
Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.
On Fri, Jun 9, 2017 at 11:05 AM, Konstantin Boudnik <co...@apache.org> wrote:
> Yey! That did the trick, thank you for your help! It'd be great to
> have this fix for sure!
> --
> Take care,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Fri, Jun 9, 2017 at 6:41 AM, Vladimir Ozerov <vo...@gridgain.com> wrote:
>> Cos,
>>
>> This is a problem with our URI parsing. Please add a slash to the end and
>> it should work: "hdfs://0f6e4ed13002.bigtop.apache.org:8020*/*". I'll
>> create a ticket for this.
>>
>> On Thu, Jun 8, 2017 at 9:28 PM, Konstantin Boudnik <co...@apache.org> wrote:
>>
>>> Thank you for your help, Vladimir. Unfortunately, I am still seeing
>>> the same behavior while attempting to bring up the service. The full
>>> element's configuration could be found at [1]
>>> Can we perhaps get on a skype/hangout for a few minutes so we can
>>> resolve this quickly? Unless, I am doing something silly and missing
>>> it, of course.
>>>
>>> That'd be a great help!
>>>
>>> [1] https://gist.github.com/c0s/cfb2b78a87f4f7f3ef4c1fa0bb5c4dea
>>>
>>> --
>>> Take care,
>>> Konstantin (Cos) Boudnik
>>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>>>
>>> Disclaimer: Opinions expressed in this email are those of the author,
>>> and do not necessarily represent the views of any company the author
>>> might be affiliated with at the moment of writing.
>>>
>>>
>>> On Thu, Jun 8, 2017 at 1:23 AM, Vladimir Ozerov <vo...@gridgain.com>
>>> wrote:
>>> > Hi Cos,
>>> >
>>> > Please try this one:
>>> >
>>> > <property name="secondaryFileSystem">
>>> > <bean
>>> > class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
>>> > <property name="fileSystemFactory">
>>> > <bean
>>> > class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
>>> > <property name="uri" value="hdfs://
>>> > 0f6e4ed13002.bigtop.apache.org:8020"/>
>>> > <property name="configPaths">
>>> > <list>
>>> > <value>/etc/hadoop/conf/core-site.xml</value>
>>> > </list>
>>> > </property>
>>> > </bean>
>>> > </property>
>>> > <property name="defaultUserName" value="ignite" />
>>> > </bean>
>>> > </property>
>>> >
>>> > Vladimir.
>>> >
>>> > On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik <co...@apache.org>
>>> wrote:
>>> >
>>> >> Guys,
>>> >>
>>> >> after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing
>>> >> a number of issues introduced by changed script interfaces and
>>> >> similar. However, the one which I still can not fix so far is this.
>>> >> The secondary file system is configured like this:
>>> >>
>>> >> <property name="fileSystemConfiguration">
>>> >> <list>
>>> >> <bean class="org.apache.ignite.configuration.
>>> >> FileSystemConfiguration"
>>> >> parent="igfsCfgBase">
>>> >> <property name="name" value="igfs"/>
>>> >>
>>> >> <!-- Caches with these names must be configured. -->
>>> >> <property name="metaCacheName" value="igfs-meta"/>
>>> >> <property name="dataCacheName" value="igfs-data"/>
>>> >>
>>> >> <!-- Configure TCP endpoint for communication with the file
>>> >> system instance. -->
>>> >> <property name="ipcEndpointConfiguration">
>>> >> <bean class="org.apache.ignite.igfs.
>>> >> IgfsIpcEndpointConfiguration">
>>> >> <property name="type" value="TCP" />
>>> >> <property name="host" value="0.0.0.0" />
>>> >> <property name="port" value="10500" />
>>> >> </bean>
>>> >> </property>
>>> >>
>>> >> <property name="secondaryFileSystem">
>>> >> <bean
>>> >> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
>>> ystem">
>>> >> <constructor-arg name="uri"
>>> >> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
>>> >> <constructor-arg name="cfgPath"
>>> >> value='/etc/hadoop/conf/core-site.xml'/>
>>> >> <constructor-arg name="userName" value="ignite"/>
>>> >> </bean>
>>> >> </property>
>>> >>
>>> >> And we are getting the following error message:
>>> >>
>>> >> Caused by: java.lang.IllegalArgumentException: Can not create a Path
>>> >> from an empty string
>>> >> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:126)
>>> >> at org.apache.hadoop.fs.Path.<init>(Path.java:134)
>>> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>>> >> HadoopBasicFileSystemFactoryDelegate.start(
>>> HadoopBasicFileSystemFactoryDe
>>> >> legate
>>> >> .java:165)
>>> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>>> >> HadoopCachingFileSystemFactoryDelegate.start(
>>> >> HadoopCachingFileSystemFactoryDele
>>> >> gate.java:58)
>>> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>>> >> HadoopIgfsSecondaryFileSystemDelegateImpl.start(
>>> >> HadoopIgfsSecondaryFileSystemDe
>>> >> legateImpl.java:375)
>>> >> at org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
>>> >> ystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:261)
>>> >> at org.apache.ignite.internal.processors.igfs.IgfsImpl.<
>>> >> init>(IgfsImpl.java:186)
>>> >> at org.apache.ignite.internal.processors.igfs.IgfsContext.<
>>> >> init>(IgfsContext.java:101)
>>> >> at org.apache.ignite.internal.processors.igfs.IgfsProcessor.
>>> >> start(IgfsProcessor.java:130)
>>> >> at org.apache.ignite.internal.IgniteKernal.startProcessor(
>>> >> IgniteKernal.java:1644)
>>> >> at org.apache.ignite.internal.IgniteKernal.start(
>>> >> IgniteKernal.java:903)
>>> >> ... 10 more
>>> >> Failed to start grid: Can not create a Path from an empty string
>>> >>
>>> >> Removing the value from cfgPath doesn't change anything. I'd
>>> >> appreciate if someone can point me to the right direction: current
>>> >> config examples aren't helping much either. Thanks!
>>> >> --
>>> >> Take care,
>>> >> Konstantin (Cos) Boudnik
>>> >> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>>> >>
>>> >> Disclaimer: Opinions expressed in this email are those of the author,
>>> >> and do not necessarily represent the views of any company the author
>>> >> might be affiliated with at the moment of writing.
>>> >>
>>>
Re: Configuration issues with IGFS in Ignite 1.9
Posted by Konstantin Boudnik <co...@apache.org>.
Yey! That did the trick, thank you for your help! It'd be great to
have this fix for sure!
--
Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.
On Fri, Jun 9, 2017 at 6:41 AM, Vladimir Ozerov <vo...@gridgain.com> wrote:
> Cos,
>
> This is a problem with our URI parsing. Please add a slash to the end and
> it should work: "hdfs://0f6e4ed13002.bigtop.apache.org:8020*/*". I'll
> create a ticket for this.
>
> On Thu, Jun 8, 2017 at 9:28 PM, Konstantin Boudnik <co...@apache.org> wrote:
>
>> Thank you for your help, Vladimir. Unfortunately, I am still seeing
>> the same behavior while attempting to bring up the service. The full
>> element's configuration could be found at [1]
>> Can we perhaps get on a skype/hangout for a few minutes so we can
>> resolve this quickly? Unless, I am doing something silly and missing
>> it, of course.
>>
>> That'd be a great help!
>>
>> [1] https://gist.github.com/c0s/cfb2b78a87f4f7f3ef4c1fa0bb5c4dea
>>
>> --
>> Take care,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>>
>> Disclaimer: Opinions expressed in this email are those of the author,
>> and do not necessarily represent the views of any company the author
>> might be affiliated with at the moment of writing.
>>
>>
>> On Thu, Jun 8, 2017 at 1:23 AM, Vladimir Ozerov <vo...@gridgain.com>
>> wrote:
>> > Hi Cos,
>> >
>> > Please try this one:
>> >
>> > <property name="secondaryFileSystem">
>> > <bean
>> > class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
>> > <property name="fileSystemFactory">
>> > <bean
>> > class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
>> > <property name="uri" value="hdfs://
>> > 0f6e4ed13002.bigtop.apache.org:8020"/>
>> > <property name="configPaths">
>> > <list>
>> > <value>/etc/hadoop/conf/core-site.xml</value>
>> > </list>
>> > </property>
>> > </bean>
>> > </property>
>> > <property name="defaultUserName" value="ignite" />
>> > </bean>
>> > </property>
>> >
>> > Vladimir.
>> >
>> > On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik <co...@apache.org>
>> wrote:
>> >
>> >> Guys,
>> >>
>> >> after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing
>> >> a number of issues introduced by changed script interfaces and
>> >> similar. However, the one which I still can not fix so far is this.
>> >> The secondary file system is configured like this:
>> >>
>> >> <property name="fileSystemConfiguration">
>> >> <list>
>> >> <bean class="org.apache.ignite.configuration.
>> >> FileSystemConfiguration"
>> >> parent="igfsCfgBase">
>> >> <property name="name" value="igfs"/>
>> >>
>> >> <!-- Caches with these names must be configured. -->
>> >> <property name="metaCacheName" value="igfs-meta"/>
>> >> <property name="dataCacheName" value="igfs-data"/>
>> >>
>> >> <!-- Configure TCP endpoint for communication with the file
>> >> system instance. -->
>> >> <property name="ipcEndpointConfiguration">
>> >> <bean class="org.apache.ignite.igfs.
>> >> IgfsIpcEndpointConfiguration">
>> >> <property name="type" value="TCP" />
>> >> <property name="host" value="0.0.0.0" />
>> >> <property name="port" value="10500" />
>> >> </bean>
>> >> </property>
>> >>
>> >> <property name="secondaryFileSystem">
>> >> <bean
>> >> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
>> ystem">
>> >> <constructor-arg name="uri"
>> >> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
>> >> <constructor-arg name="cfgPath"
>> >> value='/etc/hadoop/conf/core-site.xml'/>
>> >> <constructor-arg name="userName" value="ignite"/>
>> >> </bean>
>> >> </property>
>> >>
>> >> And we are getting the following error message:
>> >>
>> >> Caused by: java.lang.IllegalArgumentException: Can not create a Path
>> >> from an empty string
>> >> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:126)
>> >> at org.apache.hadoop.fs.Path.<init>(Path.java:134)
>> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>> >> HadoopBasicFileSystemFactoryDelegate.start(
>> HadoopBasicFileSystemFactoryDe
>> >> legate
>> >> .java:165)
>> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>> >> HadoopCachingFileSystemFactoryDelegate.start(
>> >> HadoopCachingFileSystemFactoryDele
>> >> gate.java:58)
>> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>> >> HadoopIgfsSecondaryFileSystemDelegateImpl.start(
>> >> HadoopIgfsSecondaryFileSystemDe
>> >> legateImpl.java:375)
>> >> at org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
>> >> ystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:261)
>> >> at org.apache.ignite.internal.processors.igfs.IgfsImpl.<
>> >> init>(IgfsImpl.java:186)
>> >> at org.apache.ignite.internal.processors.igfs.IgfsContext.<
>> >> init>(IgfsContext.java:101)
>> >> at org.apache.ignite.internal.processors.igfs.IgfsProcessor.
>> >> start(IgfsProcessor.java:130)
>> >> at org.apache.ignite.internal.IgniteKernal.startProcessor(
>> >> IgniteKernal.java:1644)
>> >> at org.apache.ignite.internal.IgniteKernal.start(
>> >> IgniteKernal.java:903)
>> >> ... 10 more
>> >> Failed to start grid: Can not create a Path from an empty string
>> >>
>> >> Removing the value from cfgPath doesn't change anything. I'd
>> >> appreciate if someone can point me to the right direction: current
>> >> config examples aren't helping much either. Thanks!
>> >> --
>> >> Take care,
>> >> Konstantin (Cos) Boudnik
>> >> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>> >>
>> >> Disclaimer: Opinions expressed in this email are those of the author,
>> >> and do not necessarily represent the views of any company the author
>> >> might be affiliated with at the moment of writing.
>> >>
>>
Re: Configuration issues with IGFS in Ignite 1.9
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Cos,
This is a problem with our URI parsing. Please add a slash to the end and
it should work: "hdfs://0f6e4ed13002.bigtop.apache.org:8020*/*". I'll
create a ticket for this.
On Thu, Jun 8, 2017 at 9:28 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Thank you for your help, Vladimir. Unfortunately, I am still seeing
> the same behavior while attempting to bring up the service. The full
> element's configuration could be found at [1]
> Can we perhaps get on a skype/hangout for a few minutes so we can
> resolve this quickly? Unless, I am doing something silly and missing
> it, of course.
>
> That'd be a great help!
>
> [1] https://gist.github.com/c0s/cfb2b78a87f4f7f3ef4c1fa0bb5c4dea
>
> --
> Take care,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Thu, Jun 8, 2017 at 1:23 AM, Vladimir Ozerov <vo...@gridgain.com>
> wrote:
> > Hi Cos,
> >
> > Please try this one:
> >
> > <property name="secondaryFileSystem">
> > <bean
> > class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
> > <property name="fileSystemFactory">
> > <bean
> > class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
> > <property name="uri" value="hdfs://
> > 0f6e4ed13002.bigtop.apache.org:8020"/>
> > <property name="configPaths">
> > <list>
> > <value>/etc/hadoop/conf/core-site.xml</value>
> > </list>
> > </property>
> > </bean>
> > </property>
> > <property name="defaultUserName" value="ignite" />
> > </bean>
> > </property>
> >
> > Vladimir.
> >
> > On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik <co...@apache.org>
> wrote:
> >
> >> Guys,
> >>
> >> after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing
> >> a number of issues introduced by changed script interfaces and
> >> similar. However, the one which I still can not fix so far is this.
> >> The secondary file system is configured like this:
> >>
> >> <property name="fileSystemConfiguration">
> >> <list>
> >> <bean class="org.apache.ignite.configuration.
> >> FileSystemConfiguration"
> >> parent="igfsCfgBase">
> >> <property name="name" value="igfs"/>
> >>
> >> <!-- Caches with these names must be configured. -->
> >> <property name="metaCacheName" value="igfs-meta"/>
> >> <property name="dataCacheName" value="igfs-data"/>
> >>
> >> <!-- Configure TCP endpoint for communication with the file
> >> system instance. -->
> >> <property name="ipcEndpointConfiguration">
> >> <bean class="org.apache.ignite.igfs.
> >> IgfsIpcEndpointConfiguration">
> >> <property name="type" value="TCP" />
> >> <property name="host" value="0.0.0.0" />
> >> <property name="port" value="10500" />
> >> </bean>
> >> </property>
> >>
> >> <property name="secondaryFileSystem">
> >> <bean
> >> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
> ystem">
> >> <constructor-arg name="uri"
> >> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
> >> <constructor-arg name="cfgPath"
> >> value='/etc/hadoop/conf/core-site.xml'/>
> >> <constructor-arg name="userName" value="ignite"/>
> >> </bean>
> >> </property>
> >>
> >> And we are getting the following error message:
> >>
> >> Caused by: java.lang.IllegalArgumentException: Can not create a Path
> >> from an empty string
> >> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:126)
> >> at org.apache.hadoop.fs.Path.<init>(Path.java:134)
> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
> >> HadoopBasicFileSystemFactoryDelegate.start(
> HadoopBasicFileSystemFactoryDe
> >> legate
> >> .java:165)
> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
> >> HadoopCachingFileSystemFactoryDelegate.start(
> >> HadoopCachingFileSystemFactoryDele
> >> gate.java:58)
> >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
> >> HadoopIgfsSecondaryFileSystemDelegateImpl.start(
> >> HadoopIgfsSecondaryFileSystemDe
> >> legateImpl.java:375)
> >> at org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
> >> ystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:261)
> >> at org.apache.ignite.internal.processors.igfs.IgfsImpl.<
> >> init>(IgfsImpl.java:186)
> >> at org.apache.ignite.internal.processors.igfs.IgfsContext.<
> >> init>(IgfsContext.java:101)
> >> at org.apache.ignite.internal.processors.igfs.IgfsProcessor.
> >> start(IgfsProcessor.java:130)
> >> at org.apache.ignite.internal.IgniteKernal.startProcessor(
> >> IgniteKernal.java:1644)
> >> at org.apache.ignite.internal.IgniteKernal.start(
> >> IgniteKernal.java:903)
> >> ... 10 more
> >> Failed to start grid: Can not create a Path from an empty string
> >>
> >> Removing the value from cfgPath doesn't change anything. I'd
> >> appreciate if someone can point me to the right direction: current
> >> config examples aren't helping much either. Thanks!
> >> --
> >> Take care,
> >> Konstantin (Cos) Boudnik
> >> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
> >>
> >> Disclaimer: Opinions expressed in this email are those of the author,
> >> and do not necessarily represent the views of any company the author
> >> might be affiliated with at the moment of writing.
> >>
>
Re: Configuration issues with IGFS in Ignite 1.9
Posted by Konstantin Boudnik <co...@apache.org>.
Thank you for your help, Vladimir. Unfortunately, I am still seeing
the same behavior while attempting to bring up the service. The full
element's configuration could be found at [1]
Can we perhaps get on a skype/hangout for a few minutes so we can
resolve this quickly? Unless, I am doing something silly and missing
it, of course.
That'd be a great help!
[1] https://gist.github.com/c0s/cfb2b78a87f4f7f3ef4c1fa0bb5c4dea
--
Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.
On Thu, Jun 8, 2017 at 1:23 AM, Vladimir Ozerov <vo...@gridgain.com> wrote:
> Hi Cos,
>
> Please try this one:
>
> <property name="secondaryFileSystem">
> <bean
> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
> <property name="fileSystemFactory">
> <bean
> class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
> <property name="uri" value="hdfs://
> 0f6e4ed13002.bigtop.apache.org:8020"/>
> <property name="configPaths">
> <list>
> <value>/etc/hadoop/conf/core-site.xml</value>
> </list>
> </property>
> </bean>
> </property>
> <property name="defaultUserName" value="ignite" />
> </bean>
> </property>
>
> Vladimir.
>
> On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik <co...@apache.org> wrote:
>
>> Guys,
>>
>> after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing
>> a number of issues introduced by changed script interfaces and
>> similar. However, the one which I still can not fix so far is this.
>> The secondary file system is configured like this:
>>
>> <property name="fileSystemConfiguration">
>> <list>
>> <bean class="org.apache.ignite.configuration.
>> FileSystemConfiguration"
>> parent="igfsCfgBase">
>> <property name="name" value="igfs"/>
>>
>> <!-- Caches with these names must be configured. -->
>> <property name="metaCacheName" value="igfs-meta"/>
>> <property name="dataCacheName" value="igfs-data"/>
>>
>> <!-- Configure TCP endpoint for communication with the file
>> system instance. -->
>> <property name="ipcEndpointConfiguration">
>> <bean class="org.apache.ignite.igfs.
>> IgfsIpcEndpointConfiguration">
>> <property name="type" value="TCP" />
>> <property name="host" value="0.0.0.0" />
>> <property name="port" value="10500" />
>> </bean>
>> </property>
>>
>> <property name="secondaryFileSystem">
>> <bean
>> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
>> <constructor-arg name="uri"
>> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
>> <constructor-arg name="cfgPath"
>> value='/etc/hadoop/conf/core-site.xml'/>
>> <constructor-arg name="userName" value="ignite"/>
>> </bean>
>> </property>
>>
>> And we are getting the following error message:
>>
>> Caused by: java.lang.IllegalArgumentException: Can not create a Path
>> from an empty string
>> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:126)
>> at org.apache.hadoop.fs.Path.<init>(Path.java:134)
>> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>> HadoopBasicFileSystemFactoryDelegate.start(HadoopBasicFileSystemFactoryDe
>> legate
>> .java:165)
>> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>> HadoopCachingFileSystemFactoryDelegate.start(
>> HadoopCachingFileSystemFactoryDele
>> gate.java:58)
>> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
>> HadoopIgfsSecondaryFileSystemDelegateImpl.start(
>> HadoopIgfsSecondaryFileSystemDe
>> legateImpl.java:375)
>> at org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
>> ystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:261)
>> at org.apache.ignite.internal.processors.igfs.IgfsImpl.<
>> init>(IgfsImpl.java:186)
>> at org.apache.ignite.internal.processors.igfs.IgfsContext.<
>> init>(IgfsContext.java:101)
>> at org.apache.ignite.internal.processors.igfs.IgfsProcessor.
>> start(IgfsProcessor.java:130)
>> at org.apache.ignite.internal.IgniteKernal.startProcessor(
>> IgniteKernal.java:1644)
>> at org.apache.ignite.internal.IgniteKernal.start(
>> IgniteKernal.java:903)
>> ... 10 more
>> Failed to start grid: Can not create a Path from an empty string
>>
>> Removing the value from cfgPath doesn't change anything. I'd
>> appreciate if someone can point me to the right direction: current
>> config examples aren't helping much either. Thanks!
>> --
>> Take care,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>>
>> Disclaimer: Opinions expressed in this email are those of the author,
>> and do not necessarily represent the views of any company the author
>> might be affiliated with at the moment of writing.
>>
Re: Configuration issues with IGFS in Ignite 1.9
Posted by Vladimir Ozerov <vo...@gridgain.com>.
Hi Cos,
Please try this one:
<property name="secondaryFileSystem">
<bean
class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
<property name="fileSystemFactory">
<bean
class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
<property name="uri" value="hdfs://
0f6e4ed13002.bigtop.apache.org:8020"/>
<property name="configPaths">
<list>
<value>/etc/hadoop/conf/core-site.xml</value>
</list>
</property>
</bean>
</property>
<property name="defaultUserName" value="ignite" />
</bean>
</property>
Vladimir.
On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Guys,
>
> after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing
> a number of issues introduced by changed script interfaces and
> similar. However, the one which I still can not fix so far is this.
> The secondary file system is configured like this:
>
> <property name="fileSystemConfiguration">
> <list>
> <bean class="org.apache.ignite.configuration.
> FileSystemConfiguration"
> parent="igfsCfgBase">
> <property name="name" value="igfs"/>
>
> <!-- Caches with these names must be configured. -->
> <property name="metaCacheName" value="igfs-meta"/>
> <property name="dataCacheName" value="igfs-data"/>
>
> <!-- Configure TCP endpoint for communication with the file
> system instance. -->
> <property name="ipcEndpointConfiguration">
> <bean class="org.apache.ignite.igfs.
> IgfsIpcEndpointConfiguration">
> <property name="type" value="TCP" />
> <property name="host" value="0.0.0.0" />
> <property name="port" value="10500" />
> </bean>
> </property>
>
> <property name="secondaryFileSystem">
> <bean
> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
> <constructor-arg name="uri"
> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
> <constructor-arg name="cfgPath"
> value='/etc/hadoop/conf/core-site.xml'/>
> <constructor-arg name="userName" value="ignite"/>
> </bean>
> </property>
>
> And we are getting the following error message:
>
> Caused by: java.lang.IllegalArgumentException: Can not create a Path
> from an empty string
> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:126)
> at org.apache.hadoop.fs.Path.<init>(Path.java:134)
> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
> HadoopBasicFileSystemFactoryDelegate.start(HadoopBasicFileSystemFactoryDe
> legate
> .java:165)
> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
> HadoopCachingFileSystemFactoryDelegate.start(
> HadoopCachingFileSystemFactoryDele
> gate.java:58)
> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
> HadoopIgfsSecondaryFileSystemDelegateImpl.start(
> HadoopIgfsSecondaryFileSystemDe
> legateImpl.java:375)
> at org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
> ystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:261)
> at org.apache.ignite.internal.processors.igfs.IgfsImpl.<
> init>(IgfsImpl.java:186)
> at org.apache.ignite.internal.processors.igfs.IgfsContext.<
> init>(IgfsContext.java:101)
> at org.apache.ignite.internal.processors.igfs.IgfsProcessor.
> start(IgfsProcessor.java:130)
> at org.apache.ignite.internal.IgniteKernal.startProcessor(
> IgniteKernal.java:1644)
> at org.apache.ignite.internal.IgniteKernal.start(
> IgniteKernal.java:903)
> ... 10 more
> Failed to start grid: Can not create a Path from an empty string
>
> Removing the value from cfgPath doesn't change anything. I'd
> appreciate if someone can point me to the right direction: current
> config examples aren't helping much either. Thanks!
> --
> Take care,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
Re: Configuration issues with IGFS in Ignite 1.9
Posted by Denis Magda <dm...@apache.org>.
Vova,
Could you take a look at the issue?
—
Denis
> On Jun 7, 2017, at 1:40 PM, Konstantin Boudnik <co...@apache.org> wrote:
>
> Guys,
>
> after upgrading the Bigtop stack from Ignite 1.5 to 1.9 we are seeing
> a number of issues introduced by changed script interfaces and
> similar. However, the one which I still can not fix so far is this.
> The secondary file system is configured like this:
>
> <property name="fileSystemConfiguration">
> <list>
> <bean class="org.apache.ignite.configuration.FileSystemConfiguration"
> parent="igfsCfgBase">
> <property name="name" value="igfs"/>
>
> <!-- Caches with these names must be configured. -->
> <property name="metaCacheName" value="igfs-meta"/>
> <property name="dataCacheName" value="igfs-data"/>
>
> <!-- Configure TCP endpoint for communication with the file
> system instance. -->
> <property name="ipcEndpointConfiguration">
> <bean class="org.apache.ignite.igfs.IgfsIpcEndpointConfiguration">
> <property name="type" value="TCP" />
> <property name="host" value="0.0.0.0" />
> <property name="port" value="10500" />
> </bean>
> </property>
>
> <property name="secondaryFileSystem">
> <bean
> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
> <constructor-arg name="uri"
> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
> <constructor-arg name="cfgPath"
> value='/etc/hadoop/conf/core-site.xml'/>
> <constructor-arg name="userName" value="ignite"/>
> </bean>
> </property>
>
> And we are getting the following error message:
>
> Caused by: java.lang.IllegalArgumentException: Can not create a Path
> from an empty string
> at org.apache.hadoop.fs.Path.checkPathArg(Path.java:126)
> at org.apache.hadoop.fs.Path.<init>(Path.java:134)
> at org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopBasicFileSystemFactoryDelegate.start(HadoopBasicFileSystemFactoryDelegate
> .java:165)
> at org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopCachingFileSystemFactoryDelegate.start(HadoopCachingFileSystemFactoryDele
> gate.java:58)
> at org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopIgfsSecondaryFileSystemDelegateImpl.start(HadoopIgfsSecondaryFileSystemDe
> legateImpl.java:375)
> at org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:261)
> at org.apache.ignite.internal.processors.igfs.IgfsImpl.<init>(IgfsImpl.java:186)
> at org.apache.ignite.internal.processors.igfs.IgfsContext.<init>(IgfsContext.java:101)
> at org.apache.ignite.internal.processors.igfs.IgfsProcessor.start(IgfsProcessor.java:130)
> at org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1644)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:903)
> ... 10 more
> Failed to start grid: Can not create a Path from an empty string
>
> Removing the value from cfgPath doesn't change anything. I'd
> appreciate if someone can point me to the right direction: current
> config examples aren't helping much either. Thanks!
> --
> Take care,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.