My slave polls every ten minutes, but my master only indexes once a day.
Every time my slave polls but my master has not been updated, it's recorded as a replication failure in replication.properties.
Is this expected behavior? It seems to me that this should not be considered a failure.
#Replication details
#Fri Mar 02 08:23:38 EST 2012
replicationFailedAtList=1330692602649,1330692000359,1330691401390,1330690800157,1330690200096,1330689600014,1330689000012,1330688400011,1330687800013,1330687200013
previousCycleTimeInSeconds=1418 timesFailed=1675
indexReplicatedAtList=1330694618838,1330692602649,1330692000359,1330691401390,1330690800157,1330690200096,1330689600014,1330689000012,1330688400011,1330687800013
indexReplicatedAt=1330694618838 replicationFailedAt=1330692602649
lastCycleBytesDownloaded=14445955753 timesIndexReplicated=1699
EDIT:
Master is set to replicate on Optimize.
The failed replications list stops growing after the successful replication occurs. I'm not sure when they start up again, but perhaps at some point after the master starts its update on the next day?
My understanding of replication is that the slave checks the index version and if they're different the slave pulls the new data. Considering master is set to replicate on Optimize, shouldn't the index version only increment when optimization is complete? Is there some other mechanism by which the two solr instances communicate?
EDIT:
I don't have any errors in the log. I do notice that while there are a lot of lines on startup like this:
INFO: Adding component:org.apache.solr.handler.component.SpellCheckComponent#41217e67
Mar 1, 2012 11:53:49 AM org.apache.solr.handler.component.SearchHandler inform
INFO: Adding debug component:org.apache.solr.handler.component.DebugComponent#7df1bd98
Mar 1, 2012 11:53:49 AM org.apache.solr.handler.component.SearchHandler inform
INFO: Adding component:org.apache.solr.handler.component.QueryComponent#259a8416
Mar 1, 2012 11:53:49 AM org.apache.solr.handler.component.SearchHandler inform
INFO: Adding component:org.apache.solr.handler.component.FacetComponent#4355d3a3
Mar 1, 2012 11:53:49 AM org.apache.solr.handler.component.SearchHandler inform
There is nothing about the ReplicationHandler. Still, it does successfully replicate when the master is updated.
Related
We are having solr architecture as
We are facing the frequent replication failure between master to repeater server as well as between repeater to slave servers.On checking logs found every time one of the below exceptions occurred whenever the replication have failed.
1)
2)
3)
The replication configuration of master,repeater,slave's is given below:
Commit Configuration master,repeater,slave's is given below :
Replication between master and repeater occurs every 10 mins.
Replication between repeater and slave servers occurs every 15 mins between 4-7 am and after that in every 3 hours.
Please help in replication failure issue.
We have a 3 node availability group, PRIMARY, a synchronized none readable replica and a async readable replica. We are currently doing an in place upgrade to 2016, both secondaries have been upgraded and patched so I am manually failing over the primary to the none readable secondary sync replica. When I fail over, the new PRIMARY appears fine, the readable async replica appears fine but the now new secondary goes into a none synchronized state. I have attempted to resume data movement but it fails with an error message about object explorer unable to refresh.
In the error logs I can see these errors:
***The database 'X' cannot be opened because it is version 852. This server supports version 706 and earlier. A downgrade path is not supported.
AlwaysOn Availability Groups data movement for database 'X' has been suspended for the following reason: "system" (Source ID 7; Source string: 'SUSPEND_FROM_REVALIDATION'). To resume data movement on the database, you will need to resume the database manually. For information about how to resume an availability database, see SQL Server Books Online.
Error: 948, Severity: 20, State: 102.***
I assumed this might be due to the primary being 2016 and this server being 2012 but apparently this is a legacy issue on this box, it a DEV box so not been a major concern.
Does anybody know why this is happening and what to do to resolve this?
I have a Release Management 2013 release that is stuck on a deployment step. I believe I know what happened, I just don't know how to get it moving forward.
There are multiple release templates that use the Servers with Agents to run PowerShell scripts. The situation came up that one of the releases, call it release Alpha, seemed to be stuck and I couldn't determine why, so I re-started the Microsoft Deployment Agent. The reason Alpha was stuck is that the Agent was actively working on a deployment step for a different release template, call it Beta. When I restarted the Agent, it picked up the first deployment step for Alpha and finished successfully. However, Beta never finished and is sitting in the In Progress status.
I would like to know if there is anyway for me to push the deployment step for Beta into any other status so that the whole process continues. I am under the gun here for timing, so I would appreciate any suggestions.
EDIT
After about 6 hours of waiting the release Beta finally failed. In the mean time I also attempted to restart the Release Management Monitor service. This resulted in disabling my Release Management Client app with a "License Expired" message. That message finally went away after I rebooted the server where the Release Managagement Monitor service was running.
I know you're over the initial problem, but for future (which is likely with the thick RM client) there's a table in the database which contains the current step status. Steps "In progress" will return with the following query (status = 2 is in progress):
FROM [ReleaseManagement].[dbo].[ReleaseV2ActivityLog]
where status = '2'
If you cannot wait for an unspecified duration for the timeout and also don't want the server restarted for fear of impact, you can change this status column to the value '3' which will mark the step as 'succeeded' and should move you on:
update [ReleaseManagement].[dbo].[ReleaseV2ActivityLog]
set Status = '3'
where Status = '2'
Obviously amend the query to target the correct "in progress" step by specifying the workflowID or something similarly unique.
I am trying to understand the mapping between the JVMID present in the JSESSION Cookie and the ipaddr:port of the managed server. Few questions below -
Who generates the JVMID and how does apache plugin know the JVMID of a given node. Does it get it back in the response from the server (may be as part of the Dynamic Server List?).
If we send a request to an apache with a JSESSION cookie containing a JVMID, and that apache hasn’t handled any requests yet, what would be the behavior?
Assuming that apache maintains a local mapping between JVMIDs and node addresses, how does this get updated? (specially in case of apache restart or a managed server restart)
See more at: http://middlewaremagic.com/weblogic/?p=654#comment-9054
1) The JVM ID is generated from each Weblogic server and appended to the JSESSIONID.
Apache logs the individual server HASH and maps it to the respective Managed server, and is able to send it to the same weblogic managed server as the previous request.
Here is an Example log from http://www.bea-weblogic.com/weblogic-server-support-pattern-common-diagnostic-process-for-proxy-plug-in-problems.html
Mon May 10 13:14:40 2004 getpreferredServersFromCookie: -2032354160!-457294087
Mon May 10 13:14:40 2004 GET Primary JVMID1: -2032354160
Mon May 10 13:14:40 2004 GET Secondary JVMID2: -457294087
Mon May 10 13:14:40 2004 [Found Primary]: 172.18.137.50:38625:65535
Mon May 10 13:14:40 2004 list[0].jvmid: -2032354160
Mon May 10 13:14:40 2004 secondary str: -457294087
Mon May 10 13:14:40 2004 list[1].jvmid: -457294087
Mon May 10 13:14:40 2004 secondary str: -457294087
Mon May 10 13:14:40 2004 [Found Secondary]: 172.18.137.54:38625:65535
Mon May 10 13:14:40 2004 Found 2 servers
2) If the plugin is installed on the new Apache as well, the moment Apache starts up it will ping all available Weblogic servers to report them as Live or Dead (my terms used here, not official) - while doing that health check it gets the JVMID for each available Weblogic. After that when it will receive the first request with a pre-existing JVMID - it can direct correctly.
3) there are some params like DynamicServerList ON - if it's On it keeps polling for Healthy Weblogics, if OFF then it send it to a hardcoded list only. so if On - then it's pretty dynamic
I'm migrating databases from SQL Server 2008 R2 to a new server running SQL Server 2012. I set up an alert for any severity >= 16. I have a maintenance plan that includes a log backup of all user databases every 5 minutes. After restoring about 10 databases to the new server, I started getting an alert every 30 minutes that says:
DESCRIPTION: BACKUP failed to complete the command BACKUP LOG MyDatabaseName. Check the backup application log for detailed messages.
COMMENT: (None)
JOB RUN: (None)
I searched the logs and there is nothing about a failed backup, and all the backups are fine. I get the alert every 30 minutes, so it's not happening on all of the log backups because they run every 5 minutes. And it's only for one or sometimes two databases out of the 10 that have been restored onto the new server.
I would greatly appreciate anyone that can point me in the right direction to start troubleshooting this.
The maintenance plan runs via a SQL Server Agent job. Check the history of the job. Any failures might show there.
Error level 16 is not considered critical and can be fixed by the user.
Just setup the following to monitor all alerts > level 11.
1 - Database mail
http://craftydba.com/?p=1025
2 - Operator
http://craftydba.com/?p=1085
3 - Alerts
http://craftydba.com/?p=1099
Next time you get a alert, you should get an email with details.
If you want to be real fancy, you can have the alert call a job. Log the alert in the APPLICATION log and then send the email.