Could not replicate POST operation to secondary node, failover behavior is: AllowReadsFromSecondaries

[Kenneth Truyers]

When we are calling SaveChanges on the DocumentSession, every now and then we get the following exception:

System.InvalidOperationException: Could not replicate POST operation to secondary node, failover behavior is: AllowReadsFromSecondaries

   at Raven.Client.Connection.ReplicationInformer.AssertValidOperation(String method)

   at Raven.Client.Connection.ReplicationInformer.ShouldExecuteUsing(String operationUrl, Int32 currentRequest, String method, Boolean primary)

   at Raven.Client.Connection.ReplicationInformer.ExecuteWithReplication[T](String method, String primaryUrl, OperationCredentials primaryCredentials, Int32 currentRequest, Int32 currentReadStripingBase, Func`2 operation)

   at Raven.Client.Connection.ServerClient.ExecuteWithReplication[T](String method, Func`2 operation)

   at Raven.Client.Document.DocumentSession.SaveChanges()

Could someone tell me what this exception is about? 

Is it that the secondary node is not available? If so, why does it do this synchronously, shouldn't it be doing this asynchronously? Otherwise we'd need all nodes to be online when writing to the DB.

Note: Sometimes it's PUT, sometimes POST, if that makes a difference.

[Oren Eini (Ayende Rahien)]

The default replication setting only replicate reads, you need to explicitly define the conventions fail over behavior to allow fail over of read And write
And your servers should be set as master/master

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kenneth Truyers]

We have it setup as master-slave, because we don't want to failover on write.

What is the error here then? That the main database is not available?

This happens quite often so I don't think that is the case.

[Oren Eini (Ayende Rahien)]

The only reason this particular error will happen is when the primary is not available for some reason

[Kenneth Truyers]

OK, thanks.

Is it possible to configure one client to only allow reads from the master while allowing another client to read from any node?

[Oren Eini (Ayende Rahien)]

Yes, look at the FailoverBehavior property on store.Conventions

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 

[Kenneth Truyers]

Looking further into this, today this happened twice while I'm certain that the master database was available.

I can reproduce this at the moment, so this also happens sometimes when the primary is available.

[Oren Eini (Ayende Rahien)]

Enable Fiddler, what do you see there?

[Kenneth Truyers]

This is our production environment, I can't just install fiddler there. Is there a log on the server for all incoming requests?

[Oren Eini (Ayende Rahien)]

If you have enabled debug, yes. Or if you are running in IIS, enable IIS logging.

But note that this is the _client_ connecting there. you can try this from your own machine