Re: Node Gossiping Information.

[Pranay akula]

I am using cassandra 2.1, is it possible to manually make a node to gossip
with a particular set of nodes or update gossip info to current to a
 particular node. I don't think it's possible just checking if that can be
done. As i have mentioned i occasionally see hinted handoff threads getting
hung which is delaying hints delivery stored on that node and increasing
hint compactions, Gc and load issues.


Thanks
Pranay.

On Tue, Apr 4, 2017 at 12:25 PM, Jeff Jirsa  wrote:

> Cassandra uses system.peers to record the list of peers for subsequent
> startups, but gossip state is only in memory
>
> You shouldn't ever manually need to disable/re-enable gossip unless you
> want the rest of the ring to believe a node went offline/online.
>
> What version are you using?
>
>
> On Tue, Apr 4, 2017 at 7:46 AM, Pranay akula 
> wrote:
>
>> @Jeff thanks for your reply,
>>
>> What i am trying to find is where Gossip data will be stored on, which
>> Keyspace ??  The nodes will Gossip at the time of their start or will get
>> Gossiping Data from seed nodes, What i wanted to do is can we refresh the
>> Gossiping Data with out restarting service, I often see Hinted Handoff's
>> getting hanged on Some nodes so what i am currently doing to handle that
>> situation is i am disabling and enabling Gossip  for that particular node.
>> which is currently helping but i am not  sure if it's right way to do it.
>>
>> Does  streaming_socket_timeout_in_ms parameter has any role to play for
>> Hinted Hand-off's ??
>>
>> Is there any setting in Yaml file i can change get through this
>> situation.
>>
>> Thanks
>> Pranay.
>>
>> On Tue, Apr 4, 2017 at 12:19 AM, Jeff Jirsa  wrote:
>>
>>>
>>>
>>> On 2017-04-02 11:27 (-0700), Pranay akula 
>>> wrote:
>>> > where can we check  gossip information of a node ??  I couldn't find
>>> > anything in System keyspace.
>>> >
>>> > Is it possible to update or refresh Gossiping information on a node
>>> without
>>> > restarting. Does enabling and disabling Gossip will help to refresh
>>> Gossip
>>> > information on that node.
>>> >
>>>
>>>
>>> "nodetool gossipinfo"
>>>
>>>
>>>
>>
>

Re: Node Gossiping Information.

[Jeff Jirsa]

Cassandra uses system.peers to record the list of peers for subsequent
startups, but gossip state is only in memory

You shouldn't ever manually need to disable/re-enable gossip unless you
want the rest of the ring to believe a node went offline/online.

What version are you using?

On Tue, Apr 4, 2017 at 7:46 AM, Pranay akula 
wrote:

> @Jeff thanks for your reply,
>
> What i am trying to find is where Gossip data will be stored on, which
> Keyspace ??  The nodes will Gossip at the time of their start or will get
> Gossiping Data from seed nodes, What i wanted to do is can we refresh the
> Gossiping Data with out restarting service, I often see Hinted Handoff's
> getting hanged on Some nodes so what i am currently doing to handle that
> situation is i am disabling and enabling Gossip  for that particular node.
> which is currently helping but i am not  sure if it's right way to do it.
>
> Does  streaming_socket_timeout_in_ms parameter has any role to play for
> Hinted Hand-off's ??
>
> Is there any setting in Yaml file i can change get through this situation.
>
> Thanks
> Pranay.
>
> On Tue, Apr 4, 2017 at 12:19 AM, Jeff Jirsa  wrote:
>
>>
>>
>> On 2017-04-02 11:27 (-0700), Pranay akula 
>> wrote:
>> > where can we check  gossip information of a node ??  I couldn't find
>> > anything in System keyspace.
>> >
>> > Is it possible to update or refresh Gossiping information on a node
>> without
>> > restarting. Does enabling and disabling Gossip will help to refresh
>> Gossip
>> > information on that node.
>> >
>>
>>
>> "nodetool gossipinfo"
>>
>>
>>
>

Re: Node Gossiping Information.

[Pranay akula]

@Jeff thanks for your reply,

What i am trying to find is where Gossip data will be stored on, which
Keyspace ??  The nodes will Gossip at the time of their start or will get
Gossiping Data from seed nodes, What i wanted to do is can we refresh the
Gossiping Data with out restarting service, I often see Hinted Handoff's
getting hanged on Some nodes so what i am currently doing to handle that
situation is i am disabling and enabling Gossip  for that particular node.
which is currently helping but i am not  sure if it's right way to do it.

Does  streaming_socket_timeout_in_ms parameter has any role to play for
Hinted Hand-off's ??

Is there any setting in Yaml file i can change get through this situation.

Thanks
Pranay.

On Tue, Apr 4, 2017 at 12:19 AM, Jeff Jirsa  wrote:

>
>
> On 2017-04-02 11:27 (-0700), Pranay akula 
> wrote:
> > where can we check  gossip information of a node ??  I couldn't find
> > anything in System keyspace.
> >
> > Is it possible to update or refresh Gossiping information on a node
> without
> > restarting. Does enabling and disabling Gossip will help to refresh
> Gossip
> > information on that node.
> >
>
>
> "nodetool gossipinfo"
>
>
>

Re: Node Gossiping Information.

[Jeff Jirsa]

On 2017-04-02 11:27 (-0700), Pranay akula  wrote: 
> where can we check  gossip information of a node ??  I couldn't find
> anything in System keyspace.
> 
> Is it possible to update or refresh Gossiping information on a node without
> restarting. Does enabling and disabling Gossip will help to refresh Gossip
> information on that node.
> 


"nodetool gossipinfo"

Node Gossiping Information.

[Pranay akula]

where can we check  gossip information of a node ??  I couldn't find
anything in System keyspace.

Is it possible to update or refresh Gossiping information on a node without
restarting. Does enabling and disabling Gossip will help to refresh Gossip
information on that node.



Thanks
Prany.