> My proposal is that ALL roles are always ALLOW if not specified explicitly.
As explained several times before, this is a problem for new roles introduced in future. Those roles will get turned on on all nodes after an upgrade, whether a user wants or not. A user explicitly mentions which roles his nodes want to assume, but after an upgrade he/she sees that node performing a new role. This is confusing. On Wed, Dec 8, 2021 at 2:57 AM Jan Høydahl <[email protected]> wrote: > >> Another user with a 100 node cluster who today have three overseer nodes >> that they have shielded from having data by specifying createNodeSet >> manually or by other means, can choose to adopt rhe role system, and define >> tree dedicated nodes with the overseer role but without the data role, and >> they will get exactly what they tried to achieve originally. Should they >> later wish to start using role XYZ releast in 9.x, then they wil prepare >> for that during the upgrade by starting a few nodes with role=XYZ and >> everything is explicit and no magic. >> > > My proposal will work exactly how you describe here. > > > > If it works exactly as I describe, then there is no use in adding the > complexity of role modes and different default for different roles. My > proposal is that ALL roles are always ALLOW if not specified explicitly. > Keep it simple. > > Jan > >
