How to run update query without interrupt other processes
That's the way InnoDB works anyway. Take a look at the MVCC (multi-version concurrency control - aka record-versioning or record-shadowing) mechanism which most databases use today.

If you are doing a long update and somebody wants to read a record, what the person doing the read will see is the database as it was before the update started. Then, when that long update commits, all subsequent queries will see the system post-update. This way, InnoDB's transactions are ACID, but futhermore, writers don't block readers and vice versa.

For more detail about MySQL specifics, see the manual here - then get back to us if you have more specific questions. If you're really interested in this topic, then I suggest that you read this chapter of the manual which goes into (a lot of) detail about the architecture of the InnoDB storage engine. 

The MyISAM engine exclusively uses a locking mechanism, but nobody should really be using it any more as it's now deprecated (if Bill Karwin says so, it must be true!).