Sergey, As it is becoming clear from another thread, the only configuration users will need to provide is the initial set of nodes. Everything else will be handled by Ignite automatically.
In this case, the name Baseline Topology will appear only in documentation, in which case the name is OK (that is if I am understanding the design correctly). However, the list initial set of nodes can be called initialActivationNodes. Makes sense? D. On Fri, Aug 11, 2017 at 2:46 AM, Sergey Chugunov <sergey.chugu...@gmail.com> wrote: > More options to name the concept (one may put "node set" or "topology" at > the end - for me these are interchangeable): > > > 1. essential > 2. basic > 3. completed > 4. prepared > 5. solid > 6. enduring > > To me the name must stress the fact that "node set" or "topology" contains > all nodes user is going to work with for a long run. > It is what user plans to work with and base the work on. > > Any thoughts on this? > > Thanks, > Sergey. > > On Thu, Aug 10, 2017 at 5:41 PM, Sergey Chugunov < > sergey.chugu...@gmail.com> > wrote: > > > Going down "node set" road: > > > > -fixed node set > > -established node set > > -base node set > > > > On Thu, Aug 10, 2017 at 5:23 PM, Dmitriy Setrakyan < > dsetrak...@apache.org> > > wrote: > > > >> Can we brainstorm on the names again, I am not sure we have a consensus > on > >> the name "baseline topology". This will be included in Ignite > >> configuration, so the name has to be clear. > >> > >> Some of the proposals were: > >> > >> - baseline topology > >> - minimal node set > >> - node restart set > >> - minimal topology > >> > >> Any other suggestions? > >> > >> D. > >> > >> On Thu, Aug 10, 2017 at 2:13 AM, Alexey Goncharuk < > >> alexey.goncha...@gmail.com> wrote: > >> > >> > Denis, > >> > > >> > This should be handled by the BT triggers. If I have 3 backups > >> configured, > >> > I actually won't care if my cluster will live 6 hours without an > >> additional > >> > backup. If for a partition there is only one backup left - a new BT > >> should > >> > be triggered automatically. > >> > > >> > 2017-08-10 0:33 GMT+03:00 Denis Magda <dma...@apache.org>: > >> > > >> > > Sergey, > >> > > > >> > > That’s the only concern I have: > >> > > > >> > > * 5. User takes out nodes from cluster (e.g. for maintenance > >> purposes): > >> > no > >> > > rebalance happens until user recreates BLT on new cluster > topology.* > >> > > > >> > > What if a node is crashed (or some other kind of outage) in the > >> middle of > >> > > the night and the user has to be sure that survived nodes will > >> rearrange > >> > > and rebalancing partitions? > >> > > > >> > > — > >> > > Denis > >> > > > >> > > > >> > > > On Aug 4, 2017, at 9:21 AM, Sergey Chugunov < > >> sergey.chugu...@gmail.com > >> > > > >> > > wrote: > >> > > > > >> > > > Folks, > >> > > > > >> > > > I've summarized all results from our discussion so far on wiki > page: > >> > > > https://cwiki.apache.org/confluence/display/IGNITE/ > >> > > Automatic+activation+design+-+draft > >> > > > > >> > > > I hope I reflected the most important details and going to add API > >> > > > suggestions for all use cases soon. > >> > > > > >> > > > Feel free to give feedback here or in comments under the page. > >> > > > > >> > > > Thanks, > >> > > > Sergey. > >> > > > > >> > > > On Thu, Aug 3, 2017 at 5:40 PM, Alexey Kuznetsov < > >> > akuznet...@apache.org> > >> > > > wrote: > >> > > > > >> > > >> Hi, > >> > > >> > >> > > >>>> 1. User creates new BLT using WebConsole or other tool and > >> "applies" > >> > > it > >> > > >> to brand-new cluster. > >> > > >> > >> > > >> Good idea, but we also should implement *command-line utility* > for > >> the > >> > > same > >> > > >> use case. > >> > > >> > >> > > >> -- > >> > > >> Alexey Kuznetsov > >> > > >> > >> > > > >> > > > >> > > >> > > > > >
