Alexander, frankly speaking I'm still for your original proposal - nodeName. The uniqueness specificities can be set in the doc.
-- Denis On Friday, December 30, 2016, Alexander Fedotov < alexander.fedot...@gmail.com> wrote: > Well, then may be we should go with one of the below names: > > processNodeName > jvmNodeName > runtimeNodeName > processScopedNodeName > jvmScopedNodeName > runtimeScopedNodeName > processWideNodeName > jvmWideNodeName > runtimeWideNodeName > > Regards, > Alexander > > 31 дек. 2016 г. 12:37 AM пользователь "Denis Magda" <dma...@apache.org> > написал: > > The parameter specifies a node name which has to be unique per JVM process > (if you start multiple nodes in a single process). In my understanding it > was mainly introduced to handle these multiple-nodes-per-JVM scenarios. > > However, several nodes can have the same name cluster wide. > > — > Denis > > >> On Dec 30, 2016, at 1:30 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: >> >> Now I am confused. What is the purpose of this configuration parameter? >> >> On Fri, Dec 30, 2016 at 1:15 PM, Denis Magda <dma...@apache.org> wrote: >> >>> See Val’s concern in the discussion. I’m absolutely fine with ‘nodeName’. >>> >>> — >>> Denis >>> >>>> On Dec 30, 2016, at 1:13 PM, Dmitriy Setrakyan <dsetrak...@apache.org> >>> wrote: >>>> >>>> On Fri, Dec 30, 2016 at 1:12 PM, Denis Magda <dma...@apache.org> wrote: >>>> >>>>> What’s about ‘localNodeName’? >>>>> >>>> >>>> Why is it better than "nodeName"? Isn't it obvious that the name is for >>> the >>>> local node? >>> >>> >
