[ZBXNEXT-1500] Full 64 bit space for Zabbix object in non-distributed setups Created: 2012 Nov 07 Updated: 2014 Feb 18 Resolved: 2012 Dec 22 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | API (A), Frontend (F), Server (S) |
Affects Version/s: | None |
Fix Version/s: | 2.1.0 |
Type: | New Feature Request | Priority: | Major |
Reporter: | Alexei Vladishev | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | consistency, dm, performance | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
Currently all Zabbix object IDs have complex structure for use in node-based distributed monitoring. It makes impossible use of full 64bit space for object IDs and also requires more complex SQL statements and additional computations. Zabbix should use 64 bit identifiers in non-DM setups by default for efficiency and better scalability. |
Comments |
Comment by Alexei Vladishev [ 2012 Nov 07 ] |
Initial draft of the specification is available at http://www.zabbix.org/wiki/Docs/specs/ZBXNEXT-1500. |
Comment by Alexander Vladishev [ 2012 Nov 09 ] |
Server side is ready for testing in the development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-1500 |
Comment by Alexander Vladishev [ 2012 Dec 22 ] |
GUI is ready for testing! |
Comment by Alexei Vladishev [ 2012 Dec 23 ] |
Tested, works as expected! |
Comment by Alexander Vladishev [ 2012 Dec 23 ] |
Available in version pre-2.1.0 (trunk) r32316. |
Comment by Martins Valkovskis [ 2013 Jan 10 ] |
Updated documentation: https://www.zabbix.com/documentation/2.2/manual/introduction/whatsnew220#full_64-bit_range_for_object_ids |
Comment by Alexander Vladishev [ 2013 Jan 16 ] |
Martins, thanks! I'm closing the issue. |
Comment by Oleksii Zagorskyi [ 2013 Dec 27 ] |
As a visible effect of these changes: Starting from 2.2 these parts of SQL for standalone setup are missing. |
Comment by Oleksii Zagorskyi [ 2014 Feb 18 ] |
Probably not everything is done, see |