Re: innodb_data_file_path

[Rick James]

It essentially does not matter these days. The setting dates back to the old days when some Operating Systems had a limit of 2G or 4G for maximum file size. innodb_file_per_table is a 'new' feature.

I would recommend:
innodb_data_file_path = ibdata1:100M:autoextend
innodb_file_per_table = ON

Explanation:
100M -- today's disks can easily hold that, even if you don't use it all. The "100M" could be larger or smaller with essentially no impact.
autoextend -- so you won't have to worry about crashing by hitting the end.
no ibdata2 -- no need to worry about 2G limit.
ON -- some maintenance issues benefit from putting each table in its own .ibd file, rather than bloating ibdata1.