Krishnanand Thommandra all time


 0 Collaborator

 2 Patch
9d3501523c91bd0c9b4ce35d8e8a3dd1a0164fbb, 88748c7b290d13b288055f5dea4d1c49d44db06d

9d3501523c91bd0c9b4ce35d8e8a3dd1a0164fbb | Author: Krishnanand Thommandra <devtkrishna@gmail.com>
 | 2017-11-07 01:01:29-08:00

    restrict refresh ring to heartBeat (#1015)
    
    * don't trace unless query is trace enabled
    
    When 'nodetool settraceprobability' is used,
    it's possible to get a response with trace information
    even though client did not specifically mark the query
    for tracing.
    
    * added myself as an author
    
    * restrict refresh ring to heartBeat
    
    GetHosts uses queries on control connection. Any query error will
    cause reconnection and refresh ring which calls GetHosts and thus
    deadlocks.
    
    Also it seems neater to have the ring refresh be done only by heartBeat.
    
    Fixes #928

88748c7b290d13b288055f5dea4d1c49d44db06d | Author: Krishnanand Thommandra <devtkrishna@gmail.com>
 | 2017-07-17 13:41:39+05:30

    avoid SIGSEGV by not tracing unless query is trace enabled (#940)
    
    * don't trace unless query is trace enabled
    
    When 'nodetool settraceprobability' is used,
    it's possible to get a response with trace information
    even though client did not specifically mark the query
    for tracing.
    
    * added myself as an author