@rpcbase/server 0.110.0 → 0.111.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -409,6 +409,11 @@ set-proc-title yes
409
409
  #
410
410
  proc-title-template "{title} {listen-addr} {server-mode}"
411
411
 
412
+ # Set the local environment which is used for string comparison operations, and
413
+ # also affect the performance of Lua scripts. Empty String indicates the locale
414
+ # is derived from the environment variables.
415
+ locale-collate ""
416
+
412
417
  ################################ SNAPSHOTTING ################################
413
418
 
414
419
  # Save the DB to disk.
@@ -624,11 +629,10 @@ repl-diskless-sync-delay 5
624
629
  repl-diskless-sync-max-replicas 0
625
630
 
626
631
  # -----------------------------------------------------------------------------
627
- # WARNING: RDB diskless load is experimental. Since in this setup the replica
628
- # does not immediately store an RDB on disk, it may cause data loss during
629
- # failovers. RDB diskless load + Redis modules not handling I/O reads may also
630
- # cause Redis to abort in case of I/O errors during the initial synchronization
631
- # stage with the master. Use only if you know what you are doing.
632
+ # WARNING: Since in this setup the replica does not immediately store an RDB on
633
+ # disk, it may cause data loss during failovers. RDB diskless load + Redis
634
+ # modules not handling I/O reads may cause Redis to abort in case of I/O errors
635
+ # during the initial synchronization stage with the master.
632
636
  # -----------------------------------------------------------------------------
633
637
  #
634
638
  # Replica can load the RDB it reads from the replication link directly from the
@@ -638,19 +642,22 @@ repl-diskless-sync-max-replicas 0
638
642
  # In many cases the disk is slower than the network, and storing and loading
639
643
  # the RDB file may increase replication time (and even increase the master's
640
644
  # Copy on Write memory and replica buffers).
641
- # However, parsing the RDB file directly from the socket may mean that we have
642
- # to flush the contents of the current database before the full rdb was
643
- # received. For this reason we have the following options:
645
+ # However, when parsing the RDB file directly from the socket, in order to avoid
646
+ # data loss it's only safe to flush the current dataset when the new dataset is
647
+ # fully loaded in memory, resulting in higher memory usage.
648
+ # For this reason we have the following options:
644
649
  #
645
650
  # "disabled" - Don't use diskless load (store the rdb file to the disk first)
646
- # "on-empty-db" - Use diskless load only when it is completely safe.
647
651
  # "swapdb" - Keep current db contents in RAM while parsing the data directly
648
652
  # from the socket. Replicas in this mode can keep serving current
649
- # data set while replication is in progress, except for cases where
653
+ # dataset while replication is in progress, except for cases where
650
654
  # they can't recognize master as having a data set from same
651
655
  # replication history.
652
656
  # Note that this requires sufficient memory, if you don't have it,
653
657
  # you risk an OOM kill.
658
+ # "on-empty-db" - Use diskless load only when current dataset is empty. This is
659
+ # safer and avoid having old and new dataset loaded side by side
660
+ # during replication.
654
661
  repl-diskless-load disabled
655
662
 
656
663
  # Master send PINGs to its replicas in a predefined interval. It's possible to
@@ -935,9 +942,9 @@ replica-priority 100
935
942
  # "nopass" status. After "resetpass" the user has no associated
936
943
  # passwords and there is no way to authenticate without adding
937
944
  # some password (or setting it as "nopass" later).
938
- # reset Performs the following actions: resetpass, resetkeys, off,
939
- # -@all. The user returns to the same state it has immediately
940
- # after its creation.
945
+ # reset Performs the following actions: resetpass, resetkeys, resetchannels,
946
+ # allchannels (if acl-pubsub-default is set), off, clearselectors, -@all.
947
+ # The user returns to the same state it has immediately after its creation.
941
948
  # (<options>) Create a new selector with the options specified within the
942
949
  # parentheses and attach it to the user. Each option should be
943
950
  # space separated. The first character must be ( and the last
@@ -1450,7 +1457,7 @@ appendfsync everysec
1450
1457
  # BGSAVE or BGREWRITEAOF is in progress.
1451
1458
  #
1452
1459
  # This means that while another child is saving, the durability of Redis is
1453
- # the same as "appendfsync none". In practical terms, this means that it is
1460
+ # the same as "appendfsync no". In practical terms, this means that it is
1454
1461
  # possible to lose up to 30 seconds of log in the worst scenario (with the
1455
1462
  # default Linux settings).
1456
1463
  #
@@ -1775,9 +1782,9 @@ aof-timestamp-enabled no
1775
1782
  # published in the header of the bus packets so that other nodes will be able to
1776
1783
  # correctly map the address of the node publishing the information.
1777
1784
  #
1778
- # If cluster-tls is set to yes and cluster-announce-tls-port is omitted or set
1785
+ # If tls-cluster is set to yes and cluster-announce-tls-port is omitted or set
1779
1786
  # to zero, then cluster-announce-port refers to the TLS port. Note also that
1780
- # cluster-announce-tls-port has no effect if cluster-tls is set to no.
1787
+ # cluster-announce-tls-port has no effect if tls-cluster is set to no.
1781
1788
  #
1782
1789
  # If the above options are not used, the normal Redis Cluster auto-detection
1783
1790
  # will be used instead.
@@ -1944,13 +1951,20 @@ list-max-listpack-size -2
1944
1951
  # etc.
1945
1952
  list-compress-depth 0
1946
1953
 
1947
- # Sets have a special encoding in just one case: when a set is composed
1954
+ # Sets have a special encoding when a set is composed
1948
1955
  # of just strings that happen to be integers in radix 10 in the range
1949
1956
  # of 64 bit signed integers.
1950
1957
  # The following configuration setting sets the limit in the size of the
1951
1958
  # set in order to use this special memory saving encoding.
1952
1959
  set-max-intset-entries 512
1953
1960
 
1961
+ # Sets containing non-integer values are also encoded using a memory efficient
1962
+ # data structure when they have a small number of entries, and the biggest entry
1963
+ # does not exceed a given threshold. These thresholds can be configured using
1964
+ # the following directives.
1965
+ set-max-listpack-entries 128
1966
+ set-max-listpack-value 64
1967
+
1954
1968
  # Similarly to hashes and lists, sorted sets are also specially encoded in
1955
1969
  # order to save a lot of space. This encoding is only used when the length and
1956
1970
  # elements of a sorted set are below the following limits:
@@ -2167,11 +2181,10 @@ rdb-save-incremental-fsync yes
2167
2181
  # to accumulate hits.
2168
2182
  #
2169
2183
  # The counter decay time is the time, in minutes, that must elapse in order
2170
- # for the key counter to be divided by two (or decremented if it has a value
2171
- # less <= 10).
2184
+ # for the key counter to be decremented.
2172
2185
  #
2173
- # The default value for the lfu-decay-time is 1. A special value of 0 means to
2174
- # decay the counter every time it happens to be scanned.
2186
+ # The default value for the lfu-decay-time is 1. A special value of 0 means we
2187
+ # will never decay the counter.
2175
2188
  #
2176
2189
  # lfu-log-factor 10
2177
2190
  # lfu-decay-time 1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rpcbase/server",
3
- "version": "0.110.0",
3
+ "version": "0.111.0",
4
4
  "license": "SSPL-1.0",
5
5
  "main": "./index.js",
6
6
  "bin": {