Skip to content

Refactor worker to standalone crate#118

Merged
wu-sheng merged 7 commits intoapache:masterfrom
jmjoy:refactor-worker
Aug 15, 2024
Merged

Refactor worker to standalone crate#118
wu-sheng merged 7 commits intoapache:masterfrom
jmjoy:refactor-worker

Conversation

@jmjoy
Copy link
Member

@jmjoy jmjoy commented Aug 14, 2024

I wanted to add a separate skywalking php worker binary, for php-fpm under daemon to use, but the worker's functionality was too coupled, so I first refactored the worker into a separate crate.

@jmjoy jmjoy marked this pull request as ready for review August 15, 2024 02:49
Copy link
Member

@wu-sheng wu-sheng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, this agent could run separatedly in a new OS level process? All data needs to transport cross processes?

@jmjoy
Copy link
Member Author

jmjoy commented Aug 15, 2024

Yes, processes can optionally run separately. In fact, data is currently transmitted across processes, through unix domain socket, but the process is automatically started when the extension is initialized. Now it is set to be optionally started manually separately.

@wu-sheng wu-sheng merged commit f433815 into apache:master Aug 15, 2024
@wu-sheng wu-sheng added this to the 0.8.0 milestone Aug 15, 2024
@wu-sheng wu-sheng added the enhancement New feature or request label Aug 15, 2024
@jmjoy jmjoy deleted the refactor-worker branch August 15, 2024 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants