You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Eric Evans (JIRA)" <ji...@apache.org> on 2010/08/31 01:27:54 UTC

[jira] Commented: (CASSANDRA-1446) cassandra-cli still relies on cassandra.in.sh instead of cassandra-env.sh

    [ https://issues.apache.org/jira/browse/CASSANDRA-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904409#action_12904409 ] 

Eric Evans commented on CASSANDRA-1446:
---------------------------------------

cassandra-cli never used the set of arguments from cassandra.in.sh which included (among other things) the heap size.  This was on purpose, the memory requirements of the CLI should be negligible, and there is definitely no correlation to the memory needed by the server. 

Do you know of a specific problem here? Can you provide any specifics?

> 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.