SOFA WEEKLY | Weekly Featured
Filter the weekly essence of Q&A, and synchronize the progress of open source
Welcome to leave a message and interact~
SOFA Stack ( S calable O pen Financial Architecture Stack) is a financial-level cloud- native architecture independently developed by Ant Group, which includes various components required to build a financial-level cloud-native architecture, including microservice R&D framework, RPC framework, and service registration Center, distributed timing tasks, current limiting/fusing framework, dynamic configuration push, distributed link tracking, Metrics monitoring measurement, distributed high-availability message queue, distributed transaction framework, distributed database proxy layer and other components are also in the financial The best practices tempered in the scene.
SOFAStack official website: https://www.sofastack.tech
SOFAStack: https://github.com/sofastack
SOFA Community Meeting Preview
Layotto:
Topic: Layotto community meeting
Time: March 29 (next Wednesday) at 14:00
Membership password (DingTalk): 688 824 34655
Call-in: +862759771621 (Mainland China) +8657128356288 (Mainland China)
Membership link: dingtalk:/ /dingtalkclient/page/videoConfFromCalendar?confId=1cebca80-e8cd-4f26-b529-79bac0ce7493&appendCalendarId=1&calendarId=2316789049
issue:
• 2023 Open Source Summer - Topic/Mentor Recruitment #894
• Discussion: Build various Components by yourself #902
• Hope Layotto provides high-performance communication and interaction capabilities #867
Interested students are welcome to participate. If you have any topics that you want to exchange and discuss, you can leave a message directly. Students who want to participate in community building can pay attention to the novice task list in the community, there is always one that suits you~
" Layotto ":
https://github.com/mosn/layotto/issues/907
Layotto 03/22 Community Meeting Recap
SOFAStack community contribution this week
SOFAStack GitHub issue Featured
This week, each project replied to a total of 2 issues
Welcome to submit issues on GitHub to interact with us
We will filter issues by
Reply in the form of "SOFA WEEKLY"
1.@kunple-w #916
SpringBoot 2.2 discarded logging.path, 2.3 has deleted this property, and logging.file.pat should be used.
Steps to reproduce the behavior：
- Use SOFA 3.10.0, configure logging.path according to SOFA guides, and some log files in the document do not appear after startup.
- Downgrade to the 3.2.0 version in the sample, the log file appears.
The screenshot is as follows (two attributes are configured at the same time):
A: The logs printed by sofa-common-tools in SOFA middleware, the log space and SOFABoot application are isolated. Therefore, the logging.path and logging.file.path properties can be used at the same time to define the log path of SOFA middleware and SOFABoot application respectively.
「SOFABoot」：https://github.com/sofastack/sofa-boot/issues/916
2. @shuangchengsun #263
The client goes online and offline, and Client1 is in the process of going offline. How is the status of Client1 in the routing table maintained at this time?
A: There is a timer on the data to maintain the data related to each session. If the session hangs up, the data of the hung session will be cleared after about 30s, and the client on the hung session will be connected at the same time ( removed The Client below) will automatically reconnect to other Sessions, and then add a version of the data to re-register with the Session, and the Session will send the data to that data again.
「SOFARegistry」：https://github.com/sofastack/sofa-registry/issues/263
Recommended reading this week
When the application is running, Layotto enters the CNCF cloud native panorama
MOSN Subproject Layotto: Opening a New Chapter of Service Mesh + Application Runtime
Booth recruitment｜"SOFA 5th Anniversary" Open Source Bazaar is waiting for you!
Topic introduction｜The first Occlum Meetup Beijing Station is coming!
