Hi @Vijay Kumar ,
You taking log backups on the primary does not change anything. When the log is required to be kept for a secondary, backup does not truncate the log. The secondary is simply running recovery on the database, that's all it does, applying the log received from the primary. The Write Ahead Protocol guarantees that whatever the secondary is 'recovering' is going to be identical to whatever the primary has in the database.
Here are the relevant explanations:
https://dba.stackexchange.com/questions/89670/how-alwayson-availability-group-secondary-replica-catches-up-with-primary-after
logspace used is 99%
Try to reboot each server in Availability Group in turn. If it does not work, you can try to do the shrink on the primary
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.