Our SQL 2014 AG has readable secondary column set to yes for all secondaries. Will it cause a lock down of DB transactions if we change the readable secondary to no and perform a shrink operation on the DB?

We have SQL 2014 with AG setup. We have one primary server and three secondary DB servers. The DB is in full recovery mode. Now we tried to do maintenance for logs, to do that we tried setting the column of readable secondary to no and we did shrink a test DB it worked out well. But the question is changing readable secondary column to no, does it cause any problems like DB transaction lock downs during the shrink operation?