Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[BUG] NodeBackup::spawn_replica does not release a reserved port number during failure #249

Closed
Labels
@dmitry-lipetsk

Description

@dmitry-lipetsk

Alter execution of TestTestgresCommon::test_replication_slots one port is not released.

Not released port is allocated in NodeBackup::spawn_primary that is called in NodeBackup::spawn_replica:

withclean_on_error(self.spawn_primary(name=name,
destroy=destroy))asnode:
# Assign it a master and a recovery file (private magic)
node._assign_master(self.original_node)
node._create_recovery_conf(username=self.username,slot=slot)

NodeBackup::spawn_replica uses clean_on_error to destroy newly created node but clean_on_error does not call PostgresNode::free_port.

@contextmanager
defclean_on_error(node):
"""
Context manager to wrap PostgresNode and such.
Calls cleanup() method when underlying code raises an exception.
"""
try:
yieldnode
exceptException:
# TODO: should we wrap this in try-block?
node.cleanup()
raise

Image

It seems to me, to fix this issue we can just call node.free_port method in clean_on_error immediatelly after node.cleanup.

Or we must to call node.free_port from node.cleanup.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp