-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lock objects do not fill metabase on resync_metabase
#1502
Labels
bug
Something isn't working
neofs-storage
Storage node application issues
question
Further information is requested
U2
Seriously planned
Milestone
Comments
aprasolova
pushed a commit
to aprasolova/neofs-node
that referenced
this issue
Oct 19, 2022
Signed-off-by: Evgenii Stratonikov <evgeniy@nspcc.ru>
root@vedi:/home/service# neofs-cli container create -r node1:8080 -w /etc/neofs/storage/wallet.json --policy "REP 1 IN n3 SELECT 1 FROM n3 AS n3 FILTER Node EQ node3 AS n3" --await --basic-acl public-read-write
Enter password >
container ID: 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P
awaiting...
container has been persisted on sidechain
root@vedi:/home/service# neofs-cli object put -r node3:8080 -w /etc/neofs/storage/wallet.json --file /home/service/.profile --no-progress --cid 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P
Enter password >
[/home/service/.profile] Object successfully stored
OID: 82G8FeerV8GaE7raSZyiLCwbKTuwNMvz5J7qcGPRLBqM
CID: 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P
root@vedi:/home/service# neofs-cli object lock -r node3:8080 -w /etc/neofs/storage/wallet.json --expire-at 30 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P 82G8FeerV8GaE7raSZyiLCwbKTuwNMvz5J7qcGPRLBqM
Enter password >
Lock object ID: CGqogCPVnyqM1xTGW627TLNMhUxoPBG2Y7MwU5SP1X6j
Objects successfully locked.
root@vedi:/home/service# neofs-cli object delete -r node3:8080 -w /etc/neofs/storage/wallet.json --cid 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P --oid 82G8FeerV8GaE7raSZyiLCwbKTuwNMvz5J7qcGPRLBqM
Enter password >
rpc error: remove object via client: status: code = 2050 message = object is locked
root@vedi:/home/service# systemctl restart neofs-storage
root@vedi:/home/service# neofs-cli object delete -r node3:8080 -w /etc/neofs/storage/wallet.json --cid 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P --oid 82G8FeerV8GaE7raSZyiLCwbKTuwNMvz5J7qcGPRLBqM
Enter password >
Object removed successfully.
ID: 8uu2Vug46ekFvWGqVqc8fZvNLfk7x9gLaPvtq1YdyZrx
CID: 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P
root@az:/home/service# neofs-cli object get -r node1:8080 -w /etc/neofs/storage/wallet.json --cid 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P --oid 82G8FeerV8GaE7raSZyiLCwbKTuwNMvz5J7qcGPRLBqM --file /tmp/get_object.sample --no-progress
Enter password >
rpc error: read object header: status: code = 2052 message = object already removed
root@az:/home/service# neofs-cli object get -r node2:8080 -w /etc/neofs/storage/wallet.json --cid 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P --oid 82G8FeerV8GaE7raSZyiLCwbKTuwNMvz5J7qcGPRLBqM --file /tmp/get_object.sample --no-progress
Enter password >
rpc error: read object header: status: code = 2052 message = object already removed
root@az:/home/service#
root@az:/home/service# neofs-cli object get -r node3:8080 -w /etc/neofs/storage/wallet.json --cid 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P --oid 82G8FeerV8GaE7raSZyiLCwbKTuwNMvz5J7qcGPRLBqM --file /tmp/get_object.sample --no-progress
Enter password >
rpc error: read object header: status: code = 2052 message = object already removed
root@az:/home/service# neofs-cli object get -r node4:8080 -w /etc/neofs/storage/wallet.json --cid 2w6wuU8j1JtQaq2iLa6ALqBNr3L6JfKZcAJpLGUufj3P --oid 82G8FeerV8GaE7raSZyiLCwbKTuwNMvz5J7qcGPRLBqM --file /tmp/get_object.sample --no-progress
Enter password >
rpc error: read object header: status: code = 2052 message = object already removed
root@az:/home/service# Possible reason: #1972 (comment). |
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Aug 21, 2023
The test_the_object_lock_should_be_kept_after_restarting_the_nodes test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Aug 21, 2023
The test_the_object_lock_should_be_kept_after_restarting_the_nodes test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Aug 30, 2023
The test_the_object_lock_should_be_kept_after_restarting_the_nodes test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Sep 7, 2023
The test_the_object_lock_should_be_kept_after_restarting_the_nodes test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Sep 7, 2023
The test_the_object_lock_should_be_kept_after_restarting_the_nodes test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Sep 7, 2023
The test_the_object_lock_should_be_kept_after_restarting_the_nodes test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Sep 8, 2023
The test_the_object_lock_should_be_kept_after_restarting_the_nodes test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Sep 12, 2023
The test_the_object_lock_should_be_kept_after_restarting_the_nodes test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Sep 14, 2023
The test_the_object_lock_should_be_kept_after_restarting_the_nodes test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Sep 25, 2023
The test_the_object_lock_should_be_kept_after_metabase_deletion test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Sep 25, 2023
The test_the_object_lock_should_be_kept_after_metabase_deletion test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229
added a commit
to vvarg229/neofs-testcases
that referenced
this issue
Sep 28, 2023
The test_the_object_lock_should_be_kept_after_metabase_deletion test added. This test verifies the issue nspcc-dev/neofs-node#1502 Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
Not an issue now and this one is about a 0.29.0 fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
neofs-storage
Storage node application issues
question
Further information is requested
U2
Seriously planned
Seems like it is true. SE does not call
Lock
.Needed to be verified. If true, we are losing every lock relationship on every metabase dropping.
The text was updated successfully, but these errors were encountered: