Planned maintenance scheduled April 17/18, 2019 at 11:00UTC (8:00pm US/Eastern) The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 11:00UTC (8:00pm US/Eastern)Recent Reputation History ChangesStack Overflow is getting a Meta of its ownOperation 'Split, All The Metas!' Shall Commence On April 16, 2014A Terms of Service update restricting companies that scrape your profile information without your permissionBrief outage planned for Wed, May 3, 2017 at 8pm US/Eastern (00:00 UTC) (like a fire drill for computers)Brief maintenances planned for Sat, July 8 & 22, 2017 both at 14:00 UTC (10AM US/Eastern)Brief maintenances planned for Sat, July 22, 2017 at 00:01 UTC (Fri July 21, 8pm US/Eastern)Planned maintenance scheduled for March 17, 2018 at 13:00 UTC (9AM US/Eastern)Brace yourselves: The GDPR is coming!Planned maintenance scheduled for July 14, 2018 at 13:00 UTC (9AM US/Eastern)
Merge multiple DataFrames Pandas
Is 'stolen' appropriate word?
Drawing vertical/oblique lines in Metrical tree (tikz-qtree, tipa)
What to do when moving next to a bird sanctuary with a loosely-domesticated cat?
Using dividends to reduce short term capital gains?
Keeping a retro style to sci-fi spaceships?
How to determine omitted units in a publication
What information about me do stores get via my credit card?
Hello, Goodbye, Adios, Aloha
How to handle characters who are more educated than the author?
Why not take a picture of a closer black hole?
How to read αἱμύλιος or when to aspirate
For what reasons would an animal species NOT cross a *horizontal* land bridge?
Are spiders unable to hurt humans, especially very small spiders?
60's-70's movie: home appliances revolting against the owners
Can I visit the Trinity College (Cambridge) library and see some of their rare books
Variable with quotation marks "$()"
How to make Illustrator type tool selection automatically adapt with text length
What do I do when my TA workload is more than expected?
Why are PDP-7-style microprogrammed instructions out of vogue?
Working through Single Responsibility Principle in Python when Calls are Expensive
Why can't wing-mounted spoilers be used to steepen approaches?
What is the padding with red substance inside of steak packaging?
Word for: a synonym with a positive connotation?
Planned maintenance scheduled April 17/18, 2019 at 11:00UTC (8:00pm US/Eastern)
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 11:00UTC (8:00pm US/Eastern)Recent Reputation History ChangesStack Overflow is getting a Meta of its ownOperation 'Split, All The Metas!' Shall Commence On April 16, 2014A Terms of Service update restricting companies that scrape your profile information without your permissionBrief outage planned for Wed, May 3, 2017 at 8pm US/Eastern (00:00 UTC) (like a fire drill for computers)Brief maintenances planned for Sat, July 8 & 22, 2017 both at 14:00 UTC (10AM US/Eastern)Brief maintenances planned for Sat, July 22, 2017 at 00:01 UTC (Fri July 21, 8pm US/Eastern)Planned maintenance scheduled for March 17, 2018 at 13:00 UTC (9AM US/Eastern)Brace yourselves: The GDPR is coming!Planned maintenance scheduled for July 14, 2018 at 13:00 UTC (9AM US/Eastern)
tl;dr: Planned service interruption that will impact all Stack Overflow/Stack Exchange sites, Jobs, Chat, and Teams. All sites will be read-only for up to an hour during the maintenance. Enterprise cloud hosted instances will not be impacted.
Short Version:
There will be a service degradation for up to an hour this upcoming week - possibly April 16th or 17th, 2019 at 00:00 UTC (8PM US/Eastern). During that time questions and answers will still display, job listings will still work, and job ads will still display. However, the site will be "read only," i.e. people won't appear logged-in, won't be able to add/edit new job listings, apply for jobs, create, edit or vote on questions/comments/answers, reputation won't change, etc. This should minimize the disruption to the majority of casual readers. We will display a banner on the sites stating we're 'read only' for maintenance. We expect that the site will be in a read-only state for less than an hour.
Longer More Technical Version of What’s Happening?
Background
Our primary database servers are currently running on Windows Server 2012. We have two Windows Failover Clusters, one for StackOverflow and one for StackExchange (Careers), each cluster contains 3 database servers. We will be upgrading the servers to Windows Server 2016. During the service interruption, we will be performing a failover of the servers still on Windows 2012 to the servers already on Windows 2016.
What we'll be doing
As mentioned we are using Windows Failover Clustering, along with SQL Server Always On Availability Groups, and Distributed Availability Groups to keep our data in sync across various servers, while giving us redundancy in multiple locations (NY and CO). Starting next week, we will be upgrading the operating systems across these servers to Windows Server 2016.
This upgrades involves many moving pieces, but high-level we will be doing the following next week:
Monday - we will be removing a NY server (currently a secondary) from an existing Windows Failover Cluster. The server will get a clean install of Windows Server 2016, a new Failover Cluster will be created, SQL Server 2017 will be reinstalled, and we will create new Availability Groups and new Distributed Availability Groups. By doing this, this server should start to receive data from the current primary SQL Server i.e. the one still in the old 2012 cluster.
Tuesday - the another NY Secondary will follow the same path as the one on Monday.
Wednesday - the remote secondaries in CO, will be removed from the old 2012 clusters, rebuilt, and put into the new 2016 failover clusters
At this point, we will have a GO / NO-GO on the failover. If everything goes according to plan and we feel comfortable, then we will perform the failover (scheduled maintenance) on Wednesday, April 17. If anything gets delayed or if there are unexpected issues, then we will push the maintenance to Thursday, April 18 or potentially later.
We will not be moving forward with the failover, until we are comfortable.
When we perform the maintenance, we will be pointing the applications to the new 2016 servers and performing a SQL failover of the Distributed Availability Groups. We expect that the site will be in a read-only state for about an hour. During this time, we will be making progress announcements and updates on @StackStatus, so following along there if you're interested.
This is a very complicated move that we are making, which has been fully tested in a lab environment, but you can never be sure of anything during these types of operations. As Nick Craver said:
Everyone has a plan until they get punched in the mouth - Mike Tyson
Questions or concerns?
Please post a comment or answer below; I'll do my best to address any concerns between now and the maintenance window.
discussion featured announcements
asked 10 mins ago
Taryn♦Taryn
32.4k11123183
add a comment |
tl;dr: Planned service interruption that will impact all Stack Overflow/Stack Exchange sites, Jobs, Chat, and Teams. All sites will be read-only for up to an hour during the maintenance. Enterprise cloud hosted instances will not be impacted.
Short Version:
There will be a service degradation for up to an hour this upcoming week - possibly April 16th or 17th, 2019 at 00:00 UTC (8PM US/Eastern). During that time questions and answers will still display, job listings will still work, and job ads will still display. However, the site will be "read only," i.e. people won't appear logged-in, won't be able to add/edit new job listings, apply for jobs, create, edit or vote on questions/comments/answers, reputation won't change, etc. This should minimize the disruption to the majority of casual readers. We will display a banner on the sites stating we're 'read only' for maintenance. We expect that the site will be in a read-only state for less than an hour.
Longer More Technical Version of What’s Happening?
Background
Our primary database servers are currently running on Windows Server 2012. We have two Windows Failover Clusters, one for StackOverflow and one for StackExchange (Careers), each cluster contains 3 database servers. We will be upgrading the servers to Windows Server 2016. During the service interruption, we will be performing a failover of the servers still on Windows 2012 to the servers already on Windows 2016.
What we'll be doing
As mentioned we are using Windows Failover Clustering, along with SQL Server Always On Availability Groups, and Distributed Availability Groups to keep our data in sync across various servers, while giving us redundancy in multiple locations (NY and CO). Starting next week, we will be upgrading the operating systems across these servers to Windows Server 2016.
This upgrades involves many moving pieces, but high-level we will be doing the following next week:
Monday - we will be removing a NY server (currently a secondary) from an existing Windows Failover Cluster. The server will get a clean install of Windows Server 2016, a new Failover Cluster will be created, SQL Server 2017 will be reinstalled, and we will create new Availability Groups and new Distributed Availability Groups. By doing this, this server should start to receive data from the current primary SQL Server i.e. the one still in the old 2012 cluster.
Tuesday - the another NY Secondary will follow the same path as the one on Monday.
Wednesday - the remote secondaries in CO, will be removed from the old 2012 clusters, rebuilt, and put into the new 2016 failover clusters
At this point, we will have a GO / NO-GO on the failover. If everything goes according to plan and we feel comfortable, then we will perform the failover (scheduled maintenance) on Wednesday, April 17. If anything gets delayed or if there are unexpected issues, then we will push the maintenance to Thursday, April 18 or potentially later.
We will not be moving forward with the failover, until we are comfortable.
When we perform the maintenance, we will be pointing the applications to the new 2016 servers and performing a SQL failover of the Distributed Availability Groups. We expect that the site will be in a read-only state for about an hour. During this time, we will be making progress announcements and updates on @StackStatus, so following along there if you're interested.
This is a very complicated move that we are making, which has been fully tested in a lab environment, but you can never be sure of anything during these types of operations. As Nick Craver said:
Everyone has a plan until they get punched in the mouth - Mike Tyson
Questions or concerns?
Please post a comment or answer below; I'll do my best to address any concerns between now and the maintenance window.
discussion featured announcements
asked 10 mins ago
Taryn♦Taryn
32.4k11123183
1
I'll cross some fingers for you :P
– Tim Stone
4 mins ago
@TimStone We need more than that. :)
– Taryn♦
1 min ago
Alright alright, I'll go buy some rum or something too
– Tim Stone
16 secs ago
The title says 11:00 UTC but in the body it says 00:00 UTC. Could you please clarify that? (My guess is that 11:00 UTC is a mistake since 8:00 PM US Eastern time is 00:00 UTC)
– Donald Duck
9 secs ago
add a comment |
tl;dr: Planned service interruption that will impact all Stack Overflow/Stack Exchange sites, Jobs, Chat, and Teams. All sites will be read-only for up to an hour during the maintenance. Enterprise cloud hosted instances will not be impacted.
Short Version:
There will be a service degradation for up to an hour this upcoming week - possibly April 16th or 17th, 2019 at 00:00 UTC (8PM US/Eastern). During that time questions and answers will still display, job listings will still work, and job ads will still display. However, the site will be "read only," i.e. people won't appear logged-in, won't be able to add/edit new job listings, apply for jobs, create, edit or vote on questions/comments/answers, reputation won't change, etc. This should minimize the disruption to the majority of casual readers. We will display a banner on the sites stating we're 'read only' for maintenance. We expect that the site will be in a read-only state for less than an hour.
Longer More Technical Version of What’s Happening?
Background
Our primary database servers are currently running on Windows Server 2012. We have two Windows Failover Clusters, one for StackOverflow and one for StackExchange (Careers), each cluster contains 3 database servers. We will be upgrading the servers to Windows Server 2016. During the service interruption, we will be performing a failover of the servers still on Windows 2012 to the servers already on Windows 2016.
What we'll be doing
As mentioned we are using Windows Failover Clustering, along with SQL Server Always On Availability Groups, and Distributed Availability Groups to keep our data in sync across various servers, while giving us redundancy in multiple locations (NY and CO). Starting next week, we will be upgrading the operating systems across these servers to Windows Server 2016.
This upgrades involves many moving pieces, but high-level we will be doing the following next week:
Monday - we will be removing a NY server (currently a secondary) from an existing Windows Failover Cluster. The server will get a clean install of Windows Server 2016, a new Failover Cluster will be created, SQL Server 2017 will be reinstalled, and we will create new Availability Groups and new Distributed Availability Groups. By doing this, this server should start to receive data from the current primary SQL Server i.e. the one still in the old 2012 cluster.
Tuesday - the another NY Secondary will follow the same path as the one on Monday.
Wednesday - the remote secondaries in CO, will be removed from the old 2012 clusters, rebuilt, and put into the new 2016 failover clusters
At this point, we will have a GO / NO-GO on the failover. If everything goes according to plan and we feel comfortable, then we will perform the failover (scheduled maintenance) on Wednesday, April 17. If anything gets delayed or if there are unexpected issues, then we will push the maintenance to Thursday, April 18 or potentially later.
We will not be moving forward with the failover, until we are comfortable.
When we perform the maintenance, we will be pointing the applications to the new 2016 servers and performing a SQL failover of the Distributed Availability Groups. We expect that the site will be in a read-only state for about an hour. During this time, we will be making progress announcements and updates on @StackStatus, so following along there if you're interested.
This is a very complicated move that we are making, which has been fully tested in a lab environment, but you can never be sure of anything during these types of operations. As Nick Craver said:
Everyone has a plan until they get punched in the mouth - Mike Tyson
Questions or concerns?
Please post a comment or answer below; I'll do my best to address any concerns between now and the maintenance window.
discussion featured announcements
asked 10 mins ago
Taryn♦Taryn
32.4k11123183
tl;dr: Planned service interruption that will impact all Stack Overflow/Stack Exchange sites, Jobs, Chat, and Teams. All sites will be read-only for up to an hour during the maintenance. Enterprise cloud hosted instances will not be impacted.
Short Version:
There will be a service degradation for up to an hour this upcoming week - possibly April 16th or 17th, 2019 at 00:00 UTC (8PM US/Eastern). During that time questions and answers will still display, job listings will still work, and job ads will still display. However, the site will be "read only," i.e. people won't appear logged-in, won't be able to add/edit new job listings, apply for jobs, create, edit or vote on questions/comments/answers, reputation won't change, etc. This should minimize the disruption to the majority of casual readers. We will display a banner on the sites stating we're 'read only' for maintenance. We expect that the site will be in a read-only state for less than an hour.
Longer More Technical Version of What’s Happening?
Background
Our primary database servers are currently running on Windows Server 2012. We have two Windows Failover Clusters, one for StackOverflow and one for StackExchange (Careers), each cluster contains 3 database servers. We will be upgrading the servers to Windows Server 2016. During the service interruption, we will be performing a failover of the servers still on Windows 2012 to the servers already on Windows 2016.
What we'll be doing
As mentioned we are using Windows Failover Clustering, along with SQL Server Always On Availability Groups, and Distributed Availability Groups to keep our data in sync across various servers, while giving us redundancy in multiple locations (NY and CO). Starting next week, we will be upgrading the operating systems across these servers to Windows Server 2016.
This upgrades involves many moving pieces, but high-level we will be doing the following next week:
Monday - we will be removing a NY server (currently a secondary) from an existing Windows Failover Cluster. The server will get a clean install of Windows Server 2016, a new Failover Cluster will be created, SQL Server 2017 will be reinstalled, and we will create new Availability Groups and new Distributed Availability Groups. By doing this, this server should start to receive data from the current primary SQL Server i.e. the one still in the old 2012 cluster.
Tuesday - the another NY Secondary will follow the same path as the one on Monday.
Wednesday - the remote secondaries in CO, will be removed from the old 2012 clusters, rebuilt, and put into the new 2016 failover clusters
At this point, we will have a GO / NO-GO on the failover. If everything goes according to plan and we feel comfortable, then we will perform the failover (scheduled maintenance) on Wednesday, April 17. If anything gets delayed or if there are unexpected issues, then we will push the maintenance to Thursday, April 18 or potentially later.
We will not be moving forward with the failover, until we are comfortable.
When we perform the maintenance, we will be pointing the applications to the new 2016 servers and performing a SQL failover of the Distributed Availability Groups. We expect that the site will be in a read-only state for about an hour. During this time, we will be making progress announcements and updates on @StackStatus, so following along there if you're interested.
This is a very complicated move that we are making, which has been fully tested in a lab environment, but you can never be sure of anything during these types of operations. As Nick Craver said:
Everyone has a plan until they get punched in the mouth - Mike Tyson
Questions or concerns?
Please post a comment or answer below; I'll do my best to address any concerns between now and the maintenance window.
discussion featured announcements
discussion featured announcements
asked 10 mins ago
Taryn♦Taryn
32.4k11123183
asked 10 mins ago
Taryn♦Taryn
32.4k11123183
asked 10 mins ago
Taryn♦Taryn
32.4k11123183
asked 10 mins ago
Taryn♦Taryn
32.4k11123183
asked 10 mins ago
Taryn♦Taryn
32.4k11123183
32.4k11123183
1
I'll cross some fingers for you :P
– Tim Stone
4 mins ago
@TimStone We need more than that. :)
– Taryn♦
1 min ago
Alright alright, I'll go buy some rum or something too
– Tim Stone
16 secs ago
The title says 11:00 UTC but in the body it says 00:00 UTC. Could you please clarify that? (My guess is that 11:00 UTC is a mistake since 8:00 PM US Eastern time is 00:00 UTC)
– Donald Duck
9 secs ago
add a comment |
1
I'll cross some fingers for you :P
– Tim Stone
4 mins ago
@TimStone We need more than that. :)
– Taryn♦
1 min ago
Alright alright, I'll go buy some rum or something too
– Tim Stone
16 secs ago
The title says 11:00 UTC but in the body it says 00:00 UTC. Could you please clarify that? (My guess is that 11:00 UTC is a mistake since 8:00 PM US Eastern time is 00:00 UTC)
– Donald Duck
9 secs ago
1
1
I'll cross some fingers for you :P
– Tim Stone
4 mins ago
I'll cross some fingers for you :P
– Tim Stone
4 mins ago
@TimStone We need more than that. :)
– Taryn♦
1 min ago
@TimStone We need more than that. :)
– Taryn♦
1 min ago
Alright alright, I'll go buy some rum or something too
– Tim Stone
16 secs ago
Alright alright, I'll go buy some rum or something too
– Tim Stone
16 secs ago
The title says 11:00 UTC but in the body it says 00:00 UTC. Could you please clarify that? (My guess is that 11:00 UTC is a mistake since 8:00 PM US Eastern time is 00:00 UTC)
– Donald Duck
9 secs ago
The title says 11:00 UTC but in the body it says 00:00 UTC. Could you please clarify that? (My guess is that 11:00 UTC is a mistake since 8:00 PM US Eastern time is 00:00 UTC)
– Donald Duck
9 secs ago
add a comment |
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
I'll cross some fingers for you :P
– Tim Stone
4 mins ago
@TimStone We need more than that. :)
– Taryn♦
1 min ago
Alright alright, I'll go buy some rum or something too
– Tim Stone
16 secs ago
The title says 11:00 UTC but in the body it says 00:00 UTC. Could you please clarify that? (My guess is that 11:00 UTC is a mistake since 8:00 PM US Eastern time is 00:00 UTC)
– Donald Duck
9 secs ago