t ‘sjk’ still unexpected parameters for nodetool
>>> utility.
>>>
>>> Am I missed something or ‘sjk’ available as separate rpm-package?
>>>
>>>
>>>
>>> Best regards, Ilya
>>>
>>>
>>>
>>
>>
>> We have C* 3.11.1, but ‘sjk’ still unexpected parameters for nodetool
>> utility.
>>
>> Am I missed something or ‘sjk’ available as separate rpm-package?
>>
>>
>>
>> Best regards, Ilya
>>
>>
>>
>
k’ available as separate rpm-package?
>
>
>
> Best regards, Ilya
>
>
>
> Тема: Re: read request is slow
> От: Dieudonné Madishon NGAYA
> Кому: user@cassandra.apache.org
> Копия:
>
>
>
> For your information,since cassandra 3.0, it
Hi!This is interesting note for me.We have C* 3.11.1, but ‘sjk’ still unexpected parameters for nodetool utility.Am I missed something or ‘sjk’ available as separate rpm-package?Best regards, Ilya
Тема: Re: read request is slow
От: Dieudonné Madishon NGAYA
Кому: user
oorthy, Natarajan <
>> natarajan_sundaramoor...@optum.com> wrote:
>>
>>> Also would like to know what monitoring should I setup so that if it
>>> happens again I can provide more information. Thanks
>>>
>>>
>>>
>>>
>>>
&
;> Also would like to know what monitoring should I setup so that if it
>> happens again I can provide more information. Thanks
>>
>>
>>
>>
>>
>> *From:* Jon Haddad [mailto:j...@jonhaddad.com]
>> *Sent:* Saturday, March 16, 2019 5:25 PM
>>
itoring should I setup so that if it
> happens again I can provide more information. Thanks
>
>
>
>
>
> *From:* Jon Haddad [mailto:j...@jonhaddad.com]
> *Sent:* Saturday, March 16, 2019 5:25 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: read request is slow
>
t; HEAP_NEWSIZE to 100 MB
>>
>>
>>
>> And
>>
>>
>>
>> heap with 50% of that as a starting point? Hw do I do this?
>>
>>
>>
>> Thanks
>>
>>
>>
>>
>>
>> *From:* Dieudonné Madishon NGAYA [mailto:dmng...@gmail.com
Madishon NGAYA [mailto:dmng...@gmail.com]
> *Sent:* Saturday, March 16, 2019 12:15 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: read request is slow
>
>
>
> I agreed with jon haddad , your MAX_HEAP_SIZE is very small. you have lot
> of RAM (256 GB), you can start your MA
Hi,
I want to add something:
5. do you know on which table are you getting these reads timeout ?
6. if yes, can you see if you don't have Excessive tombstone activity
7. how often do you run repair ?
8. can you send a system.log and also report of nodetool tpstats
9. Swap is enabled or not ?
B
1. What was the read request? Are you fetching a single row, a million,
something else?
2. What are your GC settings?
3. What's the hardware in use? What resources have been allocated to each
instance?
4. Did you see this issue after a single request or is the cluster under
heavy load?
If you're
3 pod deployed in openshift. Read request timed out due to GC collection. Can
you please look at below parameters and value to see if anything is out of
place? Thanks
cat cassandra.yaml
num_tokens: 256
hinted_handoff_enabled: true
hinted_handoff_throttle_in_kb: 1024
max_hints_delivery_thr
12 matches
Mail list logo