cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nate McCall <n...@riptano.com>
Subject Re: Issues getting JNA to work correctly under centos 5.5 using cassandra 0.7.0-rc1 and JNA 2.7.3
Date Mon, 29 Nov 2010 20:28:14 GMT
Ok, I was able to reproduce this with "0" as the value. Changing it to
"unlimited" will make this go away. A closer reading of the
limits.conf man page seems to leave some ambiguity when taken with the
examples:
"All items support the values -1, unlimited or infinity indicating no
limit, except for priority and nice."

I would recommend tightening this to a specific user. The line I ended
up with for the "cassandra" user was:

cassandra        -       memlock       unlimited

You probably want to add a line for nofile in there at ~ 16384 as well
while your there as that can be an issue depending on load.



On Mon, Nov 29, 2010 at 1:59 PM, Jason Pell <jason@pellcorp.com> wrote:
> *               -       memlock         0
>
>
> On Tue, Nov 30, 2010 at 4:40 AM, Nate McCall <nate@riptano.com> wrote:
>> What does the current line(s) in limits.conf look like?
>>
>> On Mon, Nov 29, 2010 at 2:01 AM,  <jasonmpell@gmail.com> wrote:
>>> I checked and /etc/security/limits.conf on redhat supports zero (0) to
>>> mean unlimited.  Here is the sample from the man page.  Notice the
>>> soft core entry.
>>>
>>> EXAMPLES
>>>       These are some example lines which might be specified in
>>>       /etc/security/limits.conf.
>>>
>>>       *               soft    core            0
>>>       *               hard    rss             10000
>>>       @student        hard    nproc           20
>>>       @faculty        soft    nproc           20
>>>       @faculty        hard    nproc           50
>>>       ftp             hard    nproc           0
>>>       @student        -       maxlogins       4
>>>
>>>
>>>
>>> On Mon, Nov 29, 2010 at 6:51 AM, Jason Pell <jasonmpell@gmail.com> wrote:
>>>> Ok that's a good point i will check - I am not sure.
>>>>
>>>> Sent from my iPhone
>>>> On Nov 29, 2010, at 5:53, Tyler Hobbs <tyler@riptano.com> wrote:
>>>>
>>>> I'm not familiar with ulimit on RedHat systems, but are you sure you
>>>> have ulimit set correctly? Did you set it to '0' or 'unlimited'?  I ask
>>>> because on a Debian system, I get this:
>>>>
>>>> thobbs@~ $ ulimit -l
>>>> unlimited
>>>>
>>>> Where you said that you got back '0'.
>>>>
>>>> - Tyler
>>>>
>>>> On Sun, Nov 28, 2010 at 1:15 AM, Jason Pell <jason@pellcorp.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I have selinux disabled via /etc/sysconfig/selinux already.  But I did
>>>>> as you suggested anyway, even restarted the whole machine again too
>>>>> and still no difference.  Do you know if there is a way to discover
>>>>> exactly what this error means?
>>>>>
>>>>> THanks
>>>>> Jason
>>>>>
>>>>> On Sat, Nov 27, 2010 at 3:59 AM, Nate McCall <nate@riptano.com>
wrote:
>>>>> > This might be an issue with selinux. You can try this quickly to
>>>>> > temporarily disable selinux enforcement:
>>>>> > /usr/sbin/setenforce 0  (as root)
>>>>> >
>>>>> > and then start cassandra as your user.
>>>>> >
>>>>> > On Fri, Nov 26, 2010 at 1:00 AM, Jason Pell <jasonmpell@gmail.com>
>>>>> > wrote:
>>>>> >> I restarted the box :-) so it's well and truly set
>>>>> >>
>>>>> >> Sent from my iPhone
>>>>> >> On Nov 26, 2010, at 17:57, Brandon Williams <driftx@gmail.com>
wrote:
>>>>> >>
>>>>> >> On Thu, Nov 25, 2010 at 10:02 PM, Jason Pell <jason@pellcorp.com>
>>>>> >> wrote:
>>>>> >>>
>>>>> >>> Hi,
>>>>> >>>
>>>>> >>> I have set the memlock limit to unlimited in /etc/security/limits.conf
>>>>> >>>
>>>>> >>> [developr@localhost apache-cassandra-0.7.0-rc1]$ ulimit
-l
>>>>> >>> 0
>>>>> >>>
>>>>> >>> Running as a non root user gets me a Unknown mlockall error
1
>>>>> >>
>>>>> >> Have you tried logging out and back in after changing limits.conf?
>>>>> >> -Brandon
>>>>> >
>>>>
>>>>
>>>
>>
>

Mime
View raw message