Hello DBA_Donny,
That particular error message of deadlock is not technically a deadlock, but something that InnoDB treats as one so it can kill it internally. You can see the message at the top telling you the search depth in the waits-for graph is too deep. Basically, you’ve got too many locks trying to happen on this table at the same time and it’s causing some internal constructs to fill up.
There are several things to try: Switch InnoDB to innodb_autoinc_lock_mode=2 which should loosen up the restrictions on the AUTO_INC locking structure, and/or set pt-osc to use a small chunk size, --chunk 1000, to “throttle” the speed of inserts.
No foreign keys referencing this table right?