[
https://issues.apache.org/jira/browse/BIGTOP-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209690#comment-14209690
]
Ilya Tikhonov commented on BIGTOP-1502:
---------------------------------------
Sorry for delay, [~cos].
I attached document. It's draft and it's not been published yet. This describes
top-level concept of using GGHA. Please read this first.
Some additional comments:
The both processors (MR and GGFS) are running by default. It doesn't need to
configure it if you don't need to use complicated dual modes of GGFS.
More detailed info about this read here:
http://hadoop.gridgain.org/latest/GGFS
http://hadoop.gridgain.org/latest/Configuration
GridGain cluster nodes don't have master and slave roles. By default all nodes
find each other in current subnetwork and each node can play master role.
I think the main issue is the classpath for Hadoop components. These jars must
be added to all client application and yarn nodes:
gridgain-core-<version>.jar
gridgain-hadoop-<version>.jar
Outside of BigTop we usual recommend to add links to this jars into
{{<hadoop_distribution>/share/hadoop/common/lib}} directory.
And about memory usage.
By default GGFS uses only heap memory is allocated in Xmx java option and MR
generally uses off-heap memory. To change this value, you should export
JVM_OPTS with all options are defined in {{bin/include/service.sh}} and change
Xmx value if it's needed.
> Improve puppet deployment for new gridgain component
> ----------------------------------------------------
>
> Key: BIGTOP-1502
> URL: https://issues.apache.org/jira/browse/BIGTOP-1502
> Project: Bigtop
> Issue Type: Bug
> Components: deployment
> Affects Versions: 0.8.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Fix For: 0.9.0
>
>
> Let's have puppet recipes that will automatically configure and bring up
> Gridgain caching layer
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
