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

client.delete_nodes on a large set of nodes can lead to timeout-disconnect #1148

Open
Nebukadneza opened this issue Oct 19, 2020 · 0 comments · May be fixed by #1149
Open

client.delete_nodes on a large set of nodes can lead to timeout-disconnect #1148

Nebukadneza opened this issue Oct 19, 2020 · 0 comments · May be fixed by #1149

Comments

@Nebukadneza
Copy link
Contributor

If using client.delete_nodes on a large set of nodes on a python-opcua server, the client will disconnect with a timeout. This is either true if the list of nodes is long, or recursive=True is used on a node with lots of childs.

(PR incoming)

Nebukadneza added a commit to Nebukadneza/python-opcua that referenced this issue Oct 19, 2020
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
Nebukadneza added a commit to Nebukadneza/python-opcua that referenced this issue Oct 21, 2020
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
JensPfeifle pushed a commit to JensPfeifle/python-opcua that referenced this issue Dec 16, 2020
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
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 a pull request may close this issue.

1 participant