Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 9 May 2016 16:35:12 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12966172.1462809649000.143549.1462811712823@Atlassian.JIRA>
In-Reply-To: <JIRA.12966172.1462809649000@Atlassian.JIRA>
References: <JIRA.12966172.1462809649000@Atlassian.JIRA> <JIRA.12966172.1462809649870@arcas>
Subject: [jira] [Updated] (CASSANDRA-11737) Add a way to disable severity in
 DynamicEndpointSnitch
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 09 May 2016 16:35:14 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-11737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-11737:
------------------------------------------
    Reviewer: Aleksey Yeschenko

> Add a way to disable severity in DynamicEndpointSnitch
> ------------------------------------------------------
>
>                 Key: CASSANDRA-11737
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11737
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jeremiah Jordan
>            Assignee: Jeremiah Jordan
>             Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>
> I have seen in a few clusters now where severity can out weigh latency in DynamicEndpointSnitch causing issues (a node that is completely overloaded CPU wise and has super high latency will get selected for queries, even though nodes with much lower latency exist, but they have a higher severity score).  There should be a way to disable the use of severity.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)