Hi! We deployed 2 new servers on Linux and cteated from them SHcluster. Captain: dynamic_captain : 1 elected_captain : Wed Feb 2 12:03:47 2022 id : 4F8CBE82-6302-4582-9FB7-48AC452AA43D initialized_flag : 1 label : sphome5 mgmt_uri : https://%%%%%%%%% min_peers_joined_flag : 1 rolling_restart_flag : 0 service_ready_flag : 1 Members: sphome5 label : sphome5 mgmt_uri : https://%%%%%%%%% mgmt_uri_alias : https://%%%%%%%%% status : Up sphome6 label : sphome6 last_conf_replication : Wed Feb 2 12:07:49 2022 mgmt_uri : https://%%%%%%%%% mgmt_uri_alias : https://%%%%%%%%% status : Up After creating the SHcluster, it is assigned a long ID (4F8CBE82-6302-4582-9FB7-48AC452AA43D). At now we need add older indexers via Search peers=>new search peers etc. Older indexers deployed on Windows Servers 2016 and 2019 When I try add new search peer after create i see that replication status is Failed. In file splunkd.log on indexer i see following error: BundleDataProcessor - File length is greater than 260, File creation may fail for C:\Program Files\Splunk\var\run\searchpeers\4F8CBE82-6302-4582-9FB7-48AC452AA43D-1643781827.82278d5fd22b73a1.tmp\apps\TA-alfa-telegram--connector\bin\ta_alfa_telegram_connector\aob_py2\cloudconnectlib\splunktacollectorlib\data_collection\ta_checkpoint_manager.py How we can change ID SHcluster (6302-4582-9FB7-48AC452AA43D) to shorter? And additional if is it inposable Could you please give any recomendation how we can solution this problem? ... View more