<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic How to fix bucket replication issues? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-bucket-replication-issues/m-p/329241#M19765</link>
    <description>&lt;P&gt;I am unable to search my indexed data from now in splunk. We have a rather large env, 53 indexers. I am seeing that there are prending_build. How to I rememdy this situation? &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;FBD33A23-C500-47E3-9E82-0AB11F56AB35
        active_bundle_id:D260DA9609DA32CC4A51CA307BEA131E
        base_generation_id:130560
        bucket_count:1910
        delayed_buckets_to_discard:
        fixup_set:
        heartbeat_started:1
        host_port_pair:10.9.1.9:8089
        indexing_disk_space:13191985758208
        is_searchable:1
        is_valid_bundle:1
        label:ip-10-9-1-9
        last_heartbeat:1517090749
        last_validated_bundle:D260DA9609DA32CC4A51CA307BEA131E
        latest_bundle_id:D260DA9609DA32CC4A51CA307BEA131E
        pending_builds:
            us_west_prod_predix_firehose~779~51A2E4CB-11EA-4585-84C7-D31FA864754C
        pending_job_count:0
        primary_count:1266
        primary_count_remote:1286
        register_search_address:10.9.1.9:8089
        replication_count:0
        replication_port:9887
        replication_use_ssl:0
        site:site2
        status:Up
        summary_replication_count:0
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Sat, 27 Jan 2018 22:12:38 GMT</pubDate>
    <dc:creator>brent_weaver</dc:creator>
    <dc:date>2018-01-27T22:12:38Z</dc:date>
    <item>
      <title>How to fix bucket replication issues?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-bucket-replication-issues/m-p/329241#M19765</link>
      <description>&lt;P&gt;I am unable to search my indexed data from now in splunk. We have a rather large env, 53 indexers. I am seeing that there are prending_build. How to I rememdy this situation? &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;FBD33A23-C500-47E3-9E82-0AB11F56AB35
        active_bundle_id:D260DA9609DA32CC4A51CA307BEA131E
        base_generation_id:130560
        bucket_count:1910
        delayed_buckets_to_discard:
        fixup_set:
        heartbeat_started:1
        host_port_pair:10.9.1.9:8089
        indexing_disk_space:13191985758208
        is_searchable:1
        is_valid_bundle:1
        label:ip-10-9-1-9
        last_heartbeat:1517090749
        last_validated_bundle:D260DA9609DA32CC4A51CA307BEA131E
        latest_bundle_id:D260DA9609DA32CC4A51CA307BEA131E
        pending_builds:
            us_west_prod_predix_firehose~779~51A2E4CB-11EA-4585-84C7-D31FA864754C
        pending_job_count:0
        primary_count:1266
        primary_count_remote:1286
        register_search_address:10.9.1.9:8089
        replication_count:0
        replication_port:9887
        replication_use_ssl:0
        site:site2
        status:Up
        summary_replication_count:0
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 27 Jan 2018 22:12:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-bucket-replication-issues/m-p/329241#M19765</guid>
      <dc:creator>brent_weaver</dc:creator>
      <dc:date>2018-01-27T22:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to fix bucket replication issues?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-bucket-replication-issues/m-p/329242#M19766</link>
      <description>&lt;P&gt;If it is a temporary replication problem time will be resolved.&lt;/P&gt;

&lt;P&gt;What is the load situation of each indexer? Is the load biased on one?&lt;/P&gt;

&lt;P&gt;In a clustered environment I know, there was a case in which loading concentrated on one indexer due to one huge log, making searching impossible.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2018 04:51:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-fix-bucket-replication-issues/m-p/329242#M19766</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2018-01-31T04:51:22Z</dc:date>
    </item>
  </channel>
</rss>

