I'm running transactional replication on SQL Server 2014 SP2 and have a publication that has over 3 days of latency and over 2 million transactions that are undistributed. The distributor, publication and subscriber are on separate servers.
I ran a tracer token and after 17 hours it hasn't reached the distributor much less the subscriber. Is there anything I can do to catch up besides dropping the subscription and recreating replication?