See www.zabbix.com for the official Zabbix site.
Support of full 64 bit address space for object IDs in non-DM setup
Owner: Alexei, Sasha
By default Zabbix should use full 64 bit space (signed int64) for all objects in standalone setup.
- SQL code should not perform any ID related filtering if running in standalone mode and it must not contain any dummy conditions like '1=1'
- Reservation of new IDs should have different allowed range for DM and standalone modes
- Existing validation (if there is any) of ID ranges should be enhanced to work differently in standalone mode
Server side details
- zabbix_server -n should verify that there are no configuration objects with IDs bigger than 99999999999999 and no historical objects (events, alerts, etc) with IDs bigger than 99999999999999999
- It should fail with error message 'Unable to convert. Some of object IDs are out of range in table "%s"' otherwise.
- Update http://www.zabbix.com/documentation/2.2/manual/introduction/whatsnew220
- Upgrade notes should be updated at http://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220
- It should be mentioned in both documents that in standalone setup Zabbix 2.2 will use full 64bit range for object IDs increasing maximum number of object of one type to 2^63
- Zabbix Manual should have more details on failure conditions for zabbix_server -n
- Zabbix Manual should be updated to have up-to-date information on format of Zabbix IDs
- Standalone setup works fine and executed SQLs do not use any filtering for IDs (both server/proxy and front-end)
- Conversion using 'zabbix_server -n N' works fine
- It should fail if some of object IDs are larger than 99999999999999
- Verify that if maximum object ID is 99999999999999, a new one will be 100000000000000
- Check that in DM mode everything works as before