You just need to remove the node from it's own seeds list so it can
bootstrap itself back into the cluster. Otherwise, it will immediately join
the cluster without streaming data from other replicas.
If you intend to promote it back as a seed node, you don't need to remove
it from the seeds list o
Hi - when replacing a dead seed node, we need to make it not a seed node before
replacing it.
To do that, you need to change the cassandra.yaml values and (I believe)
perform a rolling restart. Is the restart necessary?
Thanks.
---
On Tue, 8 Jan 2019 at 18:29, Jeff Jirsa wrote:
> Given Consul's popularity, seems like someone could make an argument that
> we should be shipping a consul-aware seed provider.
>
Elasticsearch has a very handy dedicated file-based discovery system:
https://www.elastic.co/guide/en/elasticsearch/r
jira/browse/CASSANDRA-3829 which was very
>> instructive, although a bit old.
>>
>>
>> On Mon, 7 Jan 2019 at 17:23, Jeff Jirsa wrote:
>>
>>> > On Jan 7, 2019, at 6:37 AM, Jonathan Ballet
>>> wrote:
>>> >
>>> [...]
>>>
>>
n, 7 Jan 2019 at 17:23, Jeff Jirsa wrote:
>>
>>> > On Jan 7, 2019, at 6:37 AM, Jonathan Ballet
>>> wrote:
>>> >
>>> [...]
>>>
>>> > In essence, in my example that would be:
>>> >
>>> > - decide that #2 and #3 will be the new
> On Mon, 7 Jan 2019 at 17:23, Jeff Jirsa wrote:
>
>> > On Jan 7, 2019, at 6:37 AM, Jonathan Ballet wrote:
>> >
>> [...]
>>
>> > In essence, in my example that would be:
>> >
>> > - decide that #2 and #3 will be the new seed nodes
quot;promote" a new seed node without having to restart
>>> all the nodes?
>>> In essence, in my example that would be:
>>>
>>> - decide that #2 and #3 will be the new seed nodes
>>> - update all the configuration files of all the nodes
onathan Ballet wrote:
> >
> [...]
>
> > In essence, in my example that would be:
> >
> > - decide that #2 and #3 will be the new seed nodes
> > - update all the configuration files of all the nodes to write the IP
> addresses of #2 and #3
> > -
to "promote" a new seed node without having to restart
>> all the nodes?
>> In essence, in my example that would be:
>>
>> - decide that #2 and #3 will be the new seed nodes
>> - update all the configuration files of all the nodes to write the IP
>&g
> On Jan 7, 2019, at 8:23 AM, Jeff Jirsa wrote:
>
>
>
>
>> On Jan 7, 2019, at 6:37 AM, Jonathan Ballet wrote:
>>
>> Hi,
>>
>> I'm trying to understand how seed nodes are working, when and how do they
>> play a part in
> On Jan 7, 2019, at 6:37 AM, Jonathan Ballet wrote:
>
> Hi,
>
> I'm trying to understand how seed nodes are working, when and how do they
> play a part in a Cassandra cluster, and how they should be managed and
> propagated to other nodes.
>
> I hav
my example that would be:
>
> - decide that #2 and #3 will be the new seed nodes
> - update all the configuration files of all the nodes to write the IP
> addresses of #2 and #3
> - DON'T restart any node - the new seed configuration will be picked up
> only if t
Hi,
I'm trying to understand how seed nodes are working, when and how do they
play a part in a Cassandra cluster, and how they should be managed and
propagated to other nodes.
I have a cluster of 6 Cassandra nodes (let's call them #1 to #6), on which
node #1 and #2 are seed
On Tue, Mar 6, 2018 at 8:28 PM, Jeff Jirsa wrote:
>
> Sorry, I wasnt as precise as I should have been:
>
> In 3.0 and newer, a bootstrapping node will wait until it has schema
> before it bootstraps. HOWEVER, we make the ssystem_auth/system_distributed,
> etc keyspaces as a node starts up, before
;Jeff Jirsa" wrote:
>
> On Mar 5, 2018, at 6:40 AM, Oleksandr Shulgin <
> oleksandr.shul...@zalando.de> wrote:
>
> We were deploying a second DC today with 3 seed nodes (30 nodes in total)
> and we have noticed that all seed nodes reported the following:
>
> I
On 6 Mar 2018 16:55, "Jeff Jirsa" wrote:
On Mar 6, 2018, at 12:32 AM, Oleksandr Shulgin
wrote:
On 5 Mar 2018 16:13, "Jeff Jirsa" wrote:
On Mar 5, 2018, at 6:40 AM, Oleksandr Shulgin
wrote:
We were deploying a second DC today with 3 seed nodes (30 nodes in total)
and
--
Jeff Jirsa
> On Mar 6, 2018, at 12:32 AM, Oleksandr Shulgin
> wrote:
>
> On 5 Mar 2018 16:13, "Jeff Jirsa" wrote:
>> On Mar 5, 2018, at 6:40 AM, Oleksandr Shulgin
>> wrote:
>> We were deploying a second DC today with 3 seed nodes (30 nodes in
On 5 Mar 2018 16:13, "Jeff Jirsa" wrote:
On Mar 5, 2018, at 6:40 AM, Oleksandr Shulgin
wrote:
We were deploying a second DC today with 3 seed nodes (30 nodes in total)
and we have noticed that all seed nodes reported the following:
INFO 10:20:50 Create new Keyspace: KeyspaceMet
> On Mar 5, 2018, at 6:40 AM, Oleksandr Shulgin
> wrote:
>
> Hi,
>
> We were deploying a second DC today with 3 seed nodes (30 nodes in total) and
> we have noticed that all seed nodes reported the following:
>
> INFO 10:20:50 Create new Keyspace: Keyspace
Hi,
We were deploying a second DC today with 3 seed nodes (30 nodes in total)
and we have noticed that all seed nodes reported the following:
INFO 10:20:50 Create new Keyspace: KeyspaceMetadata{name=system_traces,
params=KeyspaceParams{durable_writes=true,
replication=ReplicationParams{class
On Mon, Feb 26, 2018 at 7:05 PM, Jeff Jirsa wrote:
>
> I'll happily click the re-open button (you could have, too), but I'm not
> sure what the 'right' fix is. Feel free to move discussion to 5836.
>
Thanks, Jeff. Somehow, I don't see any control elements to change issue
status, even though I'
> update of the cluster and the first two nodes that we've updated happened
> to be seeds. They started happily with blank data directory and were
> serving read requests. Ouch. We only realized there was a problem then
> the next node that we've updated failed to start. Th
ppened
to be seeds. They started happily with blank data directory and were
serving read requests. Ouch. We only realized there was a problem then
the next node that we've updated failed to start. The only reason is that
it *did* try to bootstrap and failed.
People use to repeat "seed
Awesome, thanks for clarification.
So why new nodes can’t connect to ANY seed node's IP that is returned by DNS?
Why the IPs must be “hardcoded”?
—
Roman
> On May 1, 2017, at 2:11 PM, daemeon reiydelle wrote:
>
> Caps below for emphasis, not shouting ;{)
>
> Seed nodes
Caps below for emphasis, not shouting ;{)
Seed nodes are IDENTICAL to all other node hdfs nodes or you will wish
otherwise. Folks get confused because of terminoligy. I refer to this stuff
as "the seed node service of a normal hdfs node". ANY HDFS NODE IS ABLE TO
ACT AS A SEED NODE BY
So they are like any other “data” node… but special?
I’m so freaking confused by this seed nodes design.
—
Roman
> On May 1, 2017, at 1:37 PM, vasu gunja wrote:
>
> Seed will contain meta data + actual data too
>
> On Mon, May 1, 2017 at 3:34 PM, Roman Naumenko <mailto:ro
Seed will contain meta data + actual data too
On Mon, May 1, 2017 at 3:34 PM, Roman Naumenko wrote:
> Hi,
>
> I’d like to confirm that seed nodes doesn’t contain any data. Is it
> correct?
>
> Can the instances for seed nodes be smaller size than for data nodes?
>
Hi,
I’d like to confirm that seed nodes doesn’t contain any data. Is it correct?
Can the instances for seed nodes be smaller size than for data nodes?
Thank you
Roman
-
To unsubscribe, e-mail: user-unsubscr
On 02/11/2014 10:34 AM, sankalp kohli wrote:
If you don't have a schema, you are probably hitting this
https://issues.apache.org/jira/browse/CASSANDRA-6685
Looks like #6685 was committed to the cassandra-1.2 branch, yesterday.
SNAPSHOT artifacts can be grabbed for the latest build of each bran
If you don't have a schema, you are probably hitting this
https://issues.apache.org/jira/browse/CASSANDRA-6685
On Tue, Feb 11, 2014 at 8:22 AM, John Pyeatt wrote:
> I am trying to bring up a 6 node cluster in AWS. 3 seed nodes and 3
> non-seed nodes. One of each in each availabilit
I am trying to bring up a 6 node cluster in AWS. 3 seed nodes and 3
non-seed nodes. One of each in each availability zone with 1.2.15 and my
non-seed nodes never join the cluster. If I run 1.2.14 everything works
fine. We are not using vnodes and all of the initial_token values are
assigned based
On 29 August 2013 01:55, Ike Walker wrote:
> What is the best practice for how many seed nodes to have in a Cassandra
> cluster? I remember reading a recommendation of 2 seeds per datacenter in
> Datastax documentation for 0.7, but I'm interested to know what other
> people are
What is the best practice for how many seed nodes to have in a Cassandra
cluster? I remember reading a recommendation of 2 seeds per datacenter in
Datastax documentation for 0.7, but I'm interested to know what other people
are doing these days, especially in AWS.
I'm running a clu
> I had seed nodes ip1,ip2,ip3 as the seeds but what I didn't realize was then
> that these nodes had themselves as seeds. I am assuming that should never be
> done, is that correct.
The only reason nodes listing them selves as seeds can be a pain is during
bootstrap. Seeds
down at the same time , you
can put only three nodes.
Julien Campan
2013/6/24 Hiller, Dean
> For ease of use, we actually had a single cassandra.yaml deployed to every
> machine and a script that swapped out the token and listen address. I had
> seed nodes ip1,ip2,ip3 as the seeds b
For ease of use, we actually had a single cassandra.yaml deployed to every
machine and a script that swapped out the token and listen address. I had seed
nodes ip1,ip2,ip3 as the seeds but what I didn't realize was then that these
nodes had themselves as seeds. I am assuming that should
Yes. That would be a good jira if it is not already listed. If node is
a seed node autobootstrap and replicate_token settings should trigger
a fatal non-start because your giving c* conflicting directions.
Edward
On Fri, Oct 19, 2012 at 8:49 AM, Thomas van Neerijnen
wrote:
> Hi all
>
> I recentl
Hi all
I recently tried to replace a dead node using
-Dcassandra.replace_token=, which so far has been good to me.
However on one of my nodes this option was ignored and the node simply
picked a different token to live at and started up there.
It was a foolish mistake on my part because it was se
Dne 26.9.2011 16:37, Jonathan Ellis napsal(a):
The seed names should match what the seeds advertise as
listen_address. I can't think of a reason host names shouldn't work,
I used DNS alias, that was probably reason why it didn't worked.
The seed names should match what the seeds advertise as
listen_address. I can't think of a reason host names shouldn't work,
but as Peter said, using host names is a bad idea anyway.
2011/9/25 Radim Kolar :
> I just discovered that using host names for seed nodes in cassandra.yaml
> I just discovered that using host names for seed nodes in cassandra.yaml do
> not work. This is done on purpose?
I believe so yes, to avoid relying on DNS to map correctly given that
everything else is based on IP address. (IIRC, someone chime in if
there is a different reason.)
--
/
I just discovered that using host names for seed nodes in cassandra.yaml
do not work. This is done on purpose?
ecreate the rationale for that, I'll ping him and see if he'll comment here.
On Tue, Mar 1, 2011 at 12:04 PM, Aaron Morton <aa...@thelastpickle.com> wrote:
AFAIK it's recommended to have two seed nodes per dc.Some info on seeds here http://www.datastax.com/docs/0.7/operatio
ping him and see if he'll
> comment here.
>
>
> On Tue, Mar 1, 2011 at 12:04 PM, Aaron Morton wrote:
>
>> AFAIK it's recommended to have two seed nodes per dc.
>>
>> Some info on seeds here
>> <http://www.datastax.com/docs/0.7/operations/clust
nd see if he'll
comment here.
On Tue, Mar 1, 2011 at 12:04 PM, Aaron Morton wrote:
> AFAIK it's recommended to have two seed nodes per dc.
>
> Some info on seeds here
> <http://www.datastax.com/docs/0.7/operations/clustering>
> http://www.datastax.com/docs/0.7/ope
AFAIK it's recommended to have two seed nodes per dc.
Some info on seeds here http://www.datastax.com/docs/0.7/operations/clustering
You will need a restart.
Aaron
On 2/03/2011, at 6:08 AM, shan...@accenture.com wrote:
> How many seed nodes should I have for a cluster of 100 nodes e
How many seed nodes should I have for a cluster of 100 nodes each with about
500gb of data? Also to add seeds the nodes, must I change the seed nodes list
on all existing nodes through the Cassandra.yaml file? Will changes take effect
without restarting the node?
Shan (Susie) Lu, Analyst
47 matches
Mail list logo
