[
https://issues.apache.org/jira/browse/BIGTOP-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580463#comment-13580463
]
Bruno Mahé edited comment on BIGTOP-637 at 2/18/13 7:26 AM:
------------------------------------------------------------
Roman> It's already done as of this afternoon.
Cos> Sure. Let me take a look.
{quote}
I am not talking about "other uses". I am talking about bringing 6 HDFS + YARN
daemons in say 2 GB and then trying to run almost anything on such a cluster.
This is dreadful to say the least.
{quote}
So what is the alternative? Not starting them?
I am not sure to follow what you are proposing. Whether the daemons start on
their own or are brought up manually, they would still take the same amount of
memory. Also, I am not sure what would be the point to have a VM with just HDFS
running (except if you are bringing up a cluster, in which case you would still
have the same daemons somewhere else (using the same amount of memory) and
would need different set of VMs).
{quote}
As for the reference to Cloudera VM: this is exactly what I am referring to. It
is literally painful to watch how nothing can get started in this thing. It
crawls on all four.
{quote}
Could you define "_nothing can get started_". Last I checked, all the daemons
were starting and running fine and the ui was reacting fine.
was (Author: bmahe):
Roman> It's already done as of this afternoon.
> Update boxgrinder appliance for the coming release
> --------------------------------------------------
>
> Key: BIGTOP-637
> URL: https://issues.apache.org/jira/browse/BIGTOP-637
> Project: Bigtop
> Issue Type: Bug
> Affects Versions: 0.4.0
> Reporter: Bruno Mahé
> Assignee: Konstantin Boudnik
> Fix For: 0.6.0
>
> Attachments: BIGTOP-637.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
