How to avoid overflowing SessionInfo primary key?

Issue

Primary key of SessionInfo database table, which is used for storing information about active KieSession can overflow as its type is Integer.

Take this example of high load:

128 session x 60 seconds/minute x 60 minutes/hour x 24 hours/day x 365 x 5/7(week day)  = 2,883,291,429 records                                                          
year record  : 2,883,291,429 records
int_max      : 2,147,483,647

This would mean, that with the consistent load of 128 KieSession / sec the primary key of SessionInfo would overflow the INTEGER_MAX in less than a year.

How to approach this situation?