Data_id reached maximum value about hawkreloaded HOT 4 OPEN

Damn I've never seen such a massive database lol. I'm pretty amazed your table has been able to sustain such a beating over the years.

This is also NOT an updated HawkEye reloaded build because the data_id column should be unsigned, yet you've made it very clear yours is signed. Our max is 4,294,967,295. So using the latest build and allowing your table to regenerate would be pretty beneficial.

The best "solution" i can think of is change the 32bit integer to a 64bit allowing a wider range. That'd mean you'd max at 18,446,744,073,709,551,615, which would be INCREDIBLY difficult to hit. Or you could just begin resetting your database every X months.

from hawkreloaded.

Well, the ID is reset now, so I'll leave it like this for now.

FTB Infinity is updating to 1.10, we're just waiting on a few mods/plugins to make the switch. So I think the Infinity 1.7.10 will either die out or calm down a lot. So I doubt we'll have the same issue again.

For the new server however, I guess i'll go to a 64bit integer, just to be safe.

Thanks for the reply :)

from hawkreloaded.

Yea, I don't intend on purging old logs once I get cozy with a block logger, would prefer an option (unless it exists already) to use something like a 64-bit integer or similar

from hawkreloaded.

4,294,967,295 is an absolutely MASSIVE amount of rows and I've never heard of anyone being able to increment the number that high. The only reason Oxy was able to do it is because he's using an outdated table scheme.

If more people run into this problem, I'll happily convert our fields to 64bit.

from hawkreloaded.