Hi Ivan,
Thanks for clarification.
Actually I’ve modified the content of the following pages:
- Added “Atomatic Hadoop Configuration” section that describes the usage of
setup-hadoop with all its pros and cons for Apache Hadoop and CDH
Hi, Denis,
1) my opinion is that we'd better not mention 'setup-hadoop' script at all
(for the reasons mentioned above) and delete it in the nearest release.
2) Now Ignite is a part of BigTop distribution (see
https://issues.apache.org/jira/browse/IGNITE-665), so the old BigTop
instruction is not
Ivan, I think this should be documented, no?
On Mon, Dec 14, 2015 at 2:25 AM, Ivan V. wrote:
> To enable just an IGFS persistence there is no need to use HDFS (this
> requires Hadoop dependency, requires configured HDFS cluster, etc.).
> We have requests
On Mon, Dec 14, 2015 at 7:28 AM, Denis Magda wrote:
> Yes, this will be documented tomorrow. I want to go though all the steps
> by myself checking all other possible obstacles the user may face with.
>
Thanks, Denis!
>
> —
> Denis
>
> > On 14 дек. 2015 г., at 18:11,
Guys,
Why don't we include ignite-hadoop module in Fabric? This user simply wants
to configure HDFS as a secondary file system to ensure persistence. Not
having the opportunity to do this in Fabric looks weird to me. And actually
I don't think this is a use case for Hadoop Accelerator.
-Val
On
Valya,
Because we decide whether to load Hadoop module based on its availability
in classpath. And when Hadoop module is loaded, certain restrictions are
applied to configuration, e.g. peerClassLoadingEnabled must be false.
All this looks very inconvenient for me, but this is how things currently
Hi, Valentin,
1) first of all note that the author of the question uses not the latest
doc page, namely
http://apacheignite.gridgain.org/v1.0/docs/igfs-secondary-file-system .
This is version 1.0, while the latest is 1.5:
https://apacheignite.readme.io/docs/hadoop-accelerator. Besides, it