Is performance_schema off?
Yes I have turned off performance schema earlier it was on.
Are processes other than MySQL running?
Yes golden gate initial load.
I have decreased the buffer pool size to 768 GB. It got crashed after 24hrs but this time the problem was not same as there is no out of memory issue. This time error log is different.
InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
2017-07-03 14:46:48 7ef429143700 InnoDB: Assertion failure in thread 139587126310656 in file srv0srv.cc line 1757
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
11:46:48 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 404988 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
stack_bottom = 0 thread_stack 0x40000
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html
information that should help you find out what is causing the crash.
170703 14:46:51 mysqld_safe Number of processes running now: 0
170703 14:46:51 mysqld_safe mysqld restarted
2017-07-03 14:46:51 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-07-03 14:46:51 0 [Note] /usr/sbin/mysqld (mysqld 5.6.35-log) starting as process 120231 ...
2017-07-03 14:46:51 120231 [Note] Plugin 'FEDERATED' is disabled.
2017-07-03 14:46:51 120231 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-07-03 14:46:51 120231 [Note] InnoDB: The InnoDB memory heap is disabled
2017-07-03 14:46:51 120231 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-07-03 14:46:51 120231 [Note] InnoDB: Memory barrier is not used
2017-07-03 14:46:51 120231 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-07-03 14:46:51 120231 [Note] InnoDB: Using Linux native AIO
2017-07-03 14:46:51 120231 [Note] InnoDB: Using CPU crc32 instructions
2017-07-03 14:46:51 120231 [Note] InnoDB: Initializing buffer pool, size = 768.0G
2017-07-03 14:47:21 120231 [Note] InnoDB: Completed initialization of buffer pool
2017-07-03 14:47:25 120231 [Note] InnoDB: Highest supported file format is Barracuda.
2017-07-03 14:47:25 120231 [Note] InnoDB: Log scan progressed past the checkpoint lsn 8226843320457
2017-07-03 14:47:25 120231 [Note] InnoDB: Database was not shutdown normally!
2017-07-03 14:47:25 120231 [Note] InnoDB: Starting crash recovery.
2017-07-03 14:47:25 120231 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-07-03 14:47:29 120231 [Note] InnoDB: Restoring possible half-written data pages
2017-07-03 14:47:29 120231 [Note] InnoDB: from the doublewrite buffer...