Re: Configuration issues with IGFS in Ignite 1.9

[Konstantin Boudnik]

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  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  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  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  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 
 wrote:
 > Hi Cos,
 >
 > Please try this one:
 >
 > 
 > >>> > class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
 > 
 > >>> > class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
 > 
 > 
 > 
 > /etc/hadoop/conf/core-site.xml
 > 
 > 
 > 
 > 
 > 
 > 
 > 
 >
 > Vladimir.
 >
 > On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik 
 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:
 >>
 >> 
 >>   
 >> >>> >> parent="igfsCfgBase">
 >>   
 >>
 >>   
 >>   
 >>   
 >>
 >>   
 >>   
 >> 
 >>   
 >>   
 >>   
 >> 
 >>   
 >>
 >>   
 >> >>> >> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
 ystem">
 >>   >>> >> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
 >>   >>> >> value='/etc/hadoop/conf/core-site.xml'/>
 >>   
 >> 
 >>   
 >>
 >> 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.(Path.java:134)
 >> at org.apache.ignite.internal.processors.hadoop.impl.delegate.
 >> HadoopBasicFileSystemFactoryDelegate.start(
 HadoopBasicFileSystemFactoryDe
 >> 

Re: Configuration issues with IGFS in Ignite 1.9

[Konstantin Boudnik]

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  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  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  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 
>>> wrote:
>>> > Hi Cos,
>>> >
>>> > Please try this one:
>>> >
>>> > 
>>> > >> > class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
>>> > 
>>> > >> > class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
>>> > 
>>> > 
>>> > 
>>> > /etc/hadoop/conf/core-site.xml
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> >
>>> > Vladimir.
>>> >
>>> > On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik 
>>> 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:
>>> >>
>>> >> 
>>> >>   
>>> >> >> >> parent="igfsCfgBase">
>>> >>   
>>> >>
>>> >>   
>>> >>   
>>> >>   
>>> >>
>>> >>   
>>> >>   
>>> >> 
>>> >>   
>>> >>   
>>> >>   
>>> >> 
>>> >>   
>>> >>
>>> >>   
>>> >> >> >> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
>>> ystem">
>>> >>   >> >> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
>>> >>   >> >> value='/etc/hadoop/conf/core-site.xml'/>
>>> >>   
>>> >> 
>>> >>   
>>> >>
>>> >> 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.(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 

Re: Configuration issues with IGFS in Ignite 1.9

[Konstantin Boudnik]

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  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  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 
>> wrote:
>> > Hi Cos,
>> >
>> > Please try this one:
>> >
>> > 
>> > > > class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
>> > 
>> > > > class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
>> > 
>> > 
>> > 
>> > /etc/hadoop/conf/core-site.xml
>> > 
>> > 
>> > 
>> > 
>> > 
>> > 
>> > 
>> >
>> > Vladimir.
>> >
>> > On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik 
>> 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:
>> >>
>> >> 
>> >>   
>> >> > >> parent="igfsCfgBase">
>> >>   
>> >>
>> >>   
>> >>   
>> >>   
>> >>
>> >>   
>> >>   
>> >> 
>> >>   
>> >>   
>> >>   
>> >> 
>> >>   
>> >>
>> >>   
>> >> > >> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
>> ystem">
>> >>   > >> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
>> >>   > >> value='/etc/hadoop/conf/core-site.xml'/>
>> >>   
>> >> 
>> >>   
>> >>
>> >> 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.(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 

Re: Configuration issues with IGFS in Ignite 1.9

[Vladimir Ozerov]

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  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 
> wrote:
> > Hi Cos,
> >
> > Please try this one:
> >
> > 
> >  > class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
> > 
> >  > class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
> > 
> > 
> > 
> > /etc/hadoop/conf/core-site.xml
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > Vladimir.
> >
> > On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik 
> 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:
> >>
> >> 
> >>   
> >>  >> parent="igfsCfgBase">
> >>   
> >>
> >>   
> >>   
> >>   
> >>
> >>   
> >>   
> >> 
> >>   
> >>   
> >>   
> >> 
> >>   
> >>
> >>   
> >>  >> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileS
> ystem">
> >>>> value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
> >>>> value='/etc/hadoop/conf/core-site.xml'/>
> >>   
> >> 
> >>   
> >>
> >> 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.(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

[Konstantin Boudnik]

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  wrote:
> Hi Cos,
>
> Please try this one:
>
> 
>  class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
> 
>  class="org.apache.ignite.hadoop.fs.CachingHadoopFileSystemFactory">
> 
> 
> 
> /etc/hadoop/conf/core-site.xml
> 
> 
> 
> 
> 
> 
> 
>
> Vladimir.
>
> On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik  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:
>>
>> 
>>   
>> > parent="igfsCfgBase">
>>   
>>
>>   
>>   
>>   
>>
>>   
>>   
>> 
>>   
>>   
>>   
>> 
>>   
>>
>>   
>> > class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
>>   > value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
>>   > value='/etc/hadoop/conf/core-site.xml'/>
>>   
>> 
>>   
>>
>> 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.(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

[Vladimir Ozerov]

Hi Cos,

Please try this one:








/etc/hadoop/conf/core-site.xml








Vladimir.

On Wed, Jun 7, 2017 at 11:40 PM, Konstantin Boudnik  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:
>
> 
>   
>  parent="igfsCfgBase">
>   
>
>   
>   
>   
>
>   
>   
> 
>   
>   
>   
> 
>   
>
>   
>  class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
>value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
>value='/etc/hadoop/conf/core-site.xml'/>
>   
> 
>   
>
> 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.(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

[Denis Magda]

Vova,

Could you take a look at the issue?

—
Denis

> On Jun 7, 2017, at 1:40 PM, Konstantin Boudnik  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:
> 
>
>  
> parent="igfsCfgBase">
>  
> 
>  
>  
>  
> 
>  
>  
>
>  
>  
>  
>
>  
> 
>  
> class="org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem">
>   value='hdfs://0f6e4ed13002.bigtop.apache.org:8020'/>
>   value='/etc/hadoop/conf/core-site.xml'/>
>  
>
>  
> 
> 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.(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.(IgfsImpl.java:186)
>at 
> org.apache.ignite.internal.processors.igfs.IgfsContext.(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.

Configuration issues with IGFS in Ignite 1.9

[Konstantin Boudnik]

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:


  

  

  
  
  

  
  

  
  
  

  

  

  
  
  

  

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.(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.(IgfsImpl.java:186)
at 
org.apache.ignite.internal.processors.igfs.IgfsContext.(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.