Skip to content
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

Add batching functionality to delete_nodes to prevent timeouts #1149

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Nebukadneza
Copy link
Contributor

When delete_nodes is given a large amount of nodes, or is instructed
to recursively delete a big structure, the connection between client and
server can time out.

To remedy this, allow the user to supply a batch parameter, which
controls how many nodes are deleted in one request.

closes #1148

When `delete_nodes` is given a large amount of nodes, or is instructed
to recursively delete a big structure, the connection between client and
server can time out.

To remedy this, allow the user to supply a `batch` parameter, which
controls how many nodes are deleted in one request.

closes FreeOpcUa#1148
@oroulet
Copy link
Member

oroulet commented Nov 18, 2020

why does that help? the client must anyway wait for all chunks to be processed isnt'it?

@Nebukadneza
Copy link
Contributor Author

Indeed, in the end the client must wait until everything is processed on serverside. However, when deleting large structures, using python-opcua as client and as server, the delete operation will time out, because the server takes to long to process the single request. Allowing to batch these into managable chunks will at least keep the network-side working, and the requests themselves won’t time-out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

client.delete_nodes on a large set of nodes can lead to timeout-disconnect
2 participants