Result of selectors are the same for two replication groups #136

New issue

Open

opened 2025-12-28 18:07:10 +00:00 by sami · 2 comments

sami commented

2025-12-28 18:07:10 +00:00

Owner

Originally created by @acid-ant on GitHub (Oct 5, 2022).

Steps to Reproduce

Create container with following policy REP 1 IN X REP 1 IN Y CBF 1 SELECT 2 FROM * AS X SELECT 2 FROM * AS Y in dev environment:

@:~/workspace/neofs-node$ neofs-cli --rpc-endpoint 192.168.130.71:8080 --wallet ~/workspace/neofs-dev-env/wallets/wallet.json container create  --policy "REP 1 IN X REP 1 IN Y CBF 1 SELECT 2 FROM * AS X SELECT 2 FROM * AS Y" --await
Enter password > 
container ID: FTjced2QSmqYo4u7mzZYJnpxshc2R1PEJmPAeeB8o1WQ
awaiting...
container has been persisted on sidechain
@:~/workspace/neofs-node$

Expected Behavior

List of nodes for each replication group shouldn't be the same

Current Behavior

List of nodes for each replication group are the same:

@:~/workspace/neofs-node$ neofs-cli container nodes --cid FTjced2QSmqYo4u7mzZYJnpxshc2R1PEJmPAeeB8o1WQ --wallet ~/workspace/neofs-dev-env/wallets/wallet.json --rpc-endpoint 192.168.130.71:8080 --short
Enter password > 
Rep 1
	Node 1: 022bb4041c50d607ff871dec7e4cd7778388e0ea6849d84ccbd9aa8f32e16a8131 ONLINE /dns4/s01.neofs.devenv/tcp/8080 
	Node 2: 038c862959e56b43e20f79187c4fe9e0bc7c8c66c1603e6cf0ec7f87ab6b08dc35 ONLINE /dns4/s04.neofs.devenv/tcp/8082/tls /dns4/s04.neofs.devenv/tcp/8080 
Rep 2
	Node 1: 022bb4041c50d607ff871dec7e4cd7778388e0ea6849d84ccbd9aa8f32e16a8131 ONLINE /dns4/s01.neofs.devenv/tcp/8080 
	Node 2: 038c862959e56b43e20f79187c4fe9e0bc7c8c66c1603e6cf0ec7f87ab6b08dc35 ONLINE /dns4/s04.neofs.devenv/tcp/8082/tls /dns4/s04.neofs.devenv/tcp/8080 
@:~/workspace/neofs-node$

Environment

Dev environment

Originally created by @acid-ant on GitHub (Oct 5, 2022). ## Steps to Reproduce Create container with following policy `REP 1 IN X REP 1 IN Y CBF 1 SELECT 2 FROM * AS X SELECT 2 FROM * AS Y` in dev environment: ``` @:~/workspace/neofs-node$ neofs-cli --rpc-endpoint 192.168.130.71:8080 --wallet ~/workspace/neofs-dev-env/wallets/wallet.json container create --policy "REP 1 IN X REP 1 IN Y CBF 1 SELECT 2 FROM * AS X SELECT 2 FROM * AS Y" --await Enter password > container ID: FTjced2QSmqYo4u7mzZYJnpxshc2R1PEJmPAeeB8o1WQ awaiting... container has been persisted on sidechain @:~/workspace/neofs-node$ ``` ## Expected Behavior List of nodes for each replication group shouldn't be the same ## Current Behavior List of nodes for each replication group are the same: ``` @:~/workspace/neofs-node$ neofs-cli container nodes --cid FTjced2QSmqYo4u7mzZYJnpxshc2R1PEJmPAeeB8o1WQ --wallet ~/workspace/neofs-dev-env/wallets/wallet.json --rpc-endpoint 192.168.130.71:8080 --short Enter password > Rep 1 Node 1: 022bb4041c50d607ff871dec7e4cd7778388e0ea6849d84ccbd9aa8f32e16a8131 ONLINE /dns4/s01.neofs.devenv/tcp/8080 Node 2: 038c862959e56b43e20f79187c4fe9e0bc7c8c66c1603e6cf0ec7f87ab6b08dc35 ONLINE /dns4/s04.neofs.devenv/tcp/8082/tls /dns4/s04.neofs.devenv/tcp/8080 Rep 2 Node 1: 022bb4041c50d607ff871dec7e4cd7778388e0ea6849d84ccbd9aa8f32e16a8131 ONLINE /dns4/s01.neofs.devenv/tcp/8080 Node 2: 038c862959e56b43e20f79187c4fe9e0bc7c8c66c1603e6cf0ec7f87ab6b08dc35 ONLINE /dns4/s04.neofs.devenv/tcp/8082/tls /dns4/s04.neofs.devenv/tcp/8080 @:~/workspace/neofs-node$ ``` ## Environment Dev environment

sami added the

bug

documentation

labels

2025-12-28 18:07:10 +00:00

sami commented

2025-12-28 18:07:10 +00:00

Author

Owner

@roman-khimov commented on GitHub (Feb 2, 2023):

Related to nspcc-dev/neofs-api#254.

@roman-khimov commented on GitHub (Feb 2, 2023): Related to nspcc-dev/neofs-api#254.

sami commented

2025-12-28 18:07:10 +00:00

Author

Owner

@notimetoname commented on GitHub (May 11, 2023):

I think it is more like an API issue. Currently, it could be solved with more flexible policy and looks more like a feature than a bug. Think, it should be considered quite a big feature request.

@notimetoname commented on GitHub (May 11, 2023): I think it is more like an API issue. Currently, it could be solved with more flexible policy and looks more like a feature than a bug. Think, it should be considered quite a big feature request.