>>>
>>> The phi value is the level of suspicion a server might be down.
>>> phi_convict_threshold = suspicion level above which a server is marked down
>>>
>>>
>>> On Mon, Aug 3, 2015 at 1:29 PM, Thouraya TH
>>> wrote:
>>>
>>>> Hi a
:
>
>> You can read this paper that explains the Phi Accrual Failure detection
>> algo: http://vsedach.googlepages.com/HDY04.pdf
>>
>> The phi value is the level of suspicion a server might be down.
>> phi_convict_threshold = suspicion level above which a server i
algo: http://vsedach.googlepages.com/HDY04.pdf
>
> The phi value is the level of suspicion a server might be down.
> phi_convict_threshold = suspicion level above which a server is marked down
>
>
> On Mon, Aug 3, 2015 at 1:29 PM, Thouraya TH wrote:
>
>> Hi all,
>>
>> P
You can read this paper that explains the Phi Accrual Failure detection
algo: http://vsedach.googlepages.com/HDY04.pdf
The phi value is the level of suspicion a server might be down.
phi_convict_threshold = suspicion level above which a server is marked down
On Mon, Aug 3, 2015 at 1:29 PM
Hi all,
Please, can you explain me this sentence:
The configuration parameter phi_convict_threshold in the cassandra.yaml
file is used to control Cassandra’s sensitivity of node failure detection.
?
Thank you so much for help.
Kind regards.
Anyway, I can't find any reason to limit minimum value of
phi_convict_threshold to 5. maki
In real world you often want to have 9 because cassandra is too much
sensitive to overloaded LAN and nodes are flipping up/down often and
creating chaos in cluster if you have larger number of nodes
Hello,
The current trunk limit the value of phi_convict_threshold from 5 to 16
in DatabaseDescriptor.java.
And phi value is calculated in FailureDetector.java as
PHI_FACTOR x time_since_last_gossip / mean_heartbeat_interval
And the PHI_FACTOR is a predefined value:
PHI_FACTOR = 1 / Log(10
