![]() ![]() Note: This added protection is disabled by default in asadm 2.3.x and 2.4.x. In the example below, we want to truncate records in the namespace test with an LUT before July 4th, 2021 UTC-07:00. ![]() manage truncation, on the other hand, provides in-place protections to prevent the user from truncating records unintentionally. The asinfo commands are not as easy to use and have no protections. Before manage truncate, a user would be required to use asinfo. The new manage truncate command, added in asadm 2.3.0, allows users to truncate namespaces and sets, truncate records with a last-update-time (LUT) before a given DateTime, and undo in-progress truncations. Rather than walk you through all the tab-completion features, here is an example workflow (sorry if the text is small): So, if you are wondering which parameters are dynamically configurable or what are the acceptable values for any given parameter, asadm can help! The goal of this is to help our customers quickly change the configuration of the cluster, without all the headaches of the set-config info command. manage config tab-completion works on contexts, subcontexts, parameters, and enumerated values, but only if they are dynamically configurable. The tab-completion for manage config is an extension of what is already provided by asadm. In these cases just enter the name following the context: Admin+> manage config namespace test set testset param foo to bar But Wait. Now, there are other cases where the context is also assigned a name, like a namespace, set, and dc. Admin+> manage config network fabric param foo to bar Well, think of it as navigating to the given context, then changing the value of the parameter. Say for instance you would like to change the value of a configuration parameter foo in the network > fabric context to bar. To find the context of the parameter take a look at the configuration reference or your nf file. The UI was designed to be intuitive enough, so that by knowing the context of any given parameter, you should be able to infer the correct command. The documentation to do all this is pretty good, so rather than repeat it here, I would just like to talk about the UI design and the tab-completion feature. The manage config command allows you to change configuration parameters and logging levels, create and delete XDR datacenters, add/remove nodes from datacenters, and add/remove namespaces from datacenters. That is why in asadm 2.3.0 we introduced the manage config command, a counterpart to the pre-existing show config command. Here at Aerospike, we are trying to move our customers away from using asinfo, as much as possible. Asinfo is a lightweight tool for making raw info requests to an Aerospike node. Increase the Memory Settings of a NamespaceĬonfiguring Roster for Strong Consistencyīefore now, the only way to dynamically change Aerospike configuration was to use info commands. #Kitematic aerospike config file manualsIt is also worth noting that there are some great operations manuals showing asadm in action. The rest are simple enough, and you can take a look at the technical documentation linked above. Rather than talk about them all, I would like to discuss Dynamic Configuration, Roster Management, Truncation, and Job Management.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |