Solr cloud replication factort

[Raveendra Yerraguntla]

All,

I am using Solr 5.4 in solr cloud mode in a 8 node cluster. Used the
replication factor of 1 for creating the index, then switched to
replication factor > 1 for redundancy. With replication factor > 1, and
tried to do indexing for incremental.  When the incremental indexing
happens - getting a stack trace with the root cause pointing to write.lock
is not available. Further analysis found that there is only one write.lock
across all shards (leader and replicas).

But with replication factor of 1 , I could see write.lock across all nodes.

is this the expected behavior (one write.lock) in the solr cloud with
replication factor > 1. If so how can the indexing be done (even though it
is slow) with distributed and redundant shards?

OR

is there any config param that is missing to create write.lock across all
shards with replication factor > 1.

Appreciate your insights.


Thanks
Ravi

Re: Any issues with solr 5.4 and SAN drives

[Raveendra Yerraguntla]

Thanks Shawn and Jack !

It is a SAN network drive. I dont have other details with the type of
 drive.

At this point we switched back to local storage to reduce the variables.  I
will keep the community once we do more analysis using SAN network.

On Fri, Feb 5, 2016 at 7:13 PM, Jack Krupansky <jack.krupan...@gmail.com>
wrote:

> There are some tid bits on SAN in this post:
>
> https://www.hathitrust.org/blogs/large-scale-search/scaling-large-scale-search-from-50-volumes-5-million-volumes-and-beyond
>
> No direct answer for your load question.
>
> Who exactly is becoming read-only? The SAN or Solr? I mean, where is the
> error coming from?
>
> Ultimately a network connection is probably going to be more
> load-sensitive than having the same storage devices local to the server. It
> would come as no surprise that the SAN would attempt to shed load if the
> load becomes too extreme.
>
>
>
> -- Jack Krupansky
>
> On Fri, Feb 5, 2016 at 6:12 PM, Shawn Heisey <apa...@elyograg.org> wrote:
>
>> On 2/5/2016 9:28 AM, Raveendra Yerraguntla wrote:
>> > In our environment, we have intermittent errors(some node becomes self
>> > protecting by getting into read-only mode) when the load
>> > increases. Any one facing issues with Solr 5.4 and San storage drives?
>> >
>> > Our environment has few other variables. While narrowing the possible
>> > causes, reaching out to community for any similar experiences SAN
>> > storage drives with fast and huge load writes,
>>
>> Is the SAN mounted as a local filesystem, or mounted via a network
>> filesystem protocol like SMB or NFS?  Lucene (the search API that Solr
>> uses) sometimes has issues with file locking on network filesystems, but
>> if it looks to the operating system like a local disk, there will
>> normally be no problems.  *SOME* network storage protocols (iSCSI and
>> FibreChannel being the examples that come to mind) do count as "local",
>> but others do not.
>>
>> Thanks,
>> Shawn
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>
>

Any issues with solr 5.4 and SAN drives

[Raveendra Yerraguntla]

In our environment, we have intermittent errors(some node becomes self
protecting by getting into read-only mode) when the load increases. Any one
facing issues with Solr 5.4 and San storage drives?

Our environment has few other variables. While narrowing the possible
causes, reaching out to community for any similar experiences SAN storage
drives with fast and huge load writes,

Thank you !