[
https://issues.apache.org/jira/browse/CASSANDRA-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904433#action_12904433
]
Brandon Williams commented on CASSANDRA-1446:
---------------------------------------------
The specific problem I'm seeing here is that the user can launch cassandra
itself, but doesn't have enough memory to launch cassandra-cli afterwards, and
there isn't an intuitive way to change cassandra-cli's heap. I see
cassandra-cli's script specifically trying to include cassandra.in.sh, though,
on second look, it does not appear to be doing anything with it. Maybe we
should just remove the cassandra.in.sh cruft.
> cassandra-cli still relies on cassandra.in.sh instead of cassandra-env.sh
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-1446
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1446
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.7 beta 1
> Reporter: Brandon Williams
> Assignee: Eric Evans
> Priority: Trivial
> Fix For: 0.7 beta 2
>
>
> When we switched to cassandra-env.sh, we neglected to change the cli as well.
> This leads to people unable to launch to the client due to heap size, and
> not having any idea how to change the heap for the cli itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
