Planned maintenance scheduled April 17/18, 2019 at 00: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 00: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, 2014Graduation, site closure, and a clearer outlook on the health of SE sitesA 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)Planned maintenance scheduled for July 14, 2018 at 13:00 UTC (9AM US/Eastern)
Road tyres vs "Street" tyres for charity ride on MTB Tandem
Windows 10: How to Lock (not sleep) laptop on lid close?
Why can't wing-mounted spoilers be used to steepen approaches?
Python - Fishing Simulator
Who or what is the being for whom Being is a question for Heidegger?
How did passengers keep warm on sail ships?
Why does this iterative way of solving of equation work?
How are presidential pardons supposed to be used?
What was the last x86 CPU that did not have the x87 floating-point unit built in?
University's motivation for having tenure-track positions
What aspect of planet Earth must be changed to prevent the industrial revolution?
How can I define good in a religion that claims no moral authority?
How is simplicity better than precision and clarity in prose?
How should I replace vector<uint8_t>::const_iterator in an API?
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
Is this wall load bearing? Blueprints and photos attached
Can smartphones with the same camera sensor have different image quality?
He got a vote 80% that of Emmanuel Macron’s
Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?
Are my PIs rude or am I just being too sensitive?
Is there a writing software that you can sort scenes like slides in PowerPoint?
In horse breeding, what is the female equivalent of putting a horse out "to stud"?
Netflix Recommendations?
What can I do if neighbor is blocking my solar panels intentionally?
Planned maintenance scheduled April 17/18, 2019 at 00: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 00: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, 2014Graduation, site closure, and a clearer outlook on the health of SE sitesA 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)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 17th or 18th, 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 yesterday
Taryn♦Taryn
32.7k11124186
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 17th or 18th, 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 yesterday
Taryn♦Taryn
32.7k11124186
12
I'll cross some fingers for you :P
– Tim Stone
yesterday
5
@TimStone We need more than that. :)
– Taryn♦
yesterday
3
Alright alright, I'll go buy some rum or something too
– Tim Stone
yesterday
44
As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?
– rene
yesterday
3
@rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.
– Taryn♦
yesterday
7
Wait... will I have to... go to sleep!?
– Artemis Fowl
yesterday
6
Looking forward to the upgrade to Server 2019 in six to eight weeks.
– Michael Hampton
yesterday
4
@MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.
– Taryn♦
yesterday
16
🔺 Thanks for plenty of notice.
– Rob
yesterday
Thanks for the early notice; this will give companies using Stack Overflow Team time to plan what to do
– MilkyWay90
13 hours ago
Banner text: We're 'read only' for 60 to 80 minutes for maintenance.
– TGrif
10 hours 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 17th or 18th, 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 yesterday
Taryn♦Taryn
32.7k11124186
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 17th or 18th, 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 yesterday
Taryn♦Taryn
32.7k11124186
asked yesterday
Taryn♦Taryn
32.7k11124186
edited yesterday
Taryn
asked yesterday
Taryn♦Taryn
32.7k11124186
asked yesterday
Taryn♦Taryn
32.7k11124186
asked yesterday
Taryn♦Taryn
32.7k11124186
32.7k11124186
12
I'll cross some fingers for you :P
– Tim Stone
yesterday
5
@TimStone We need more than that. :)
– Taryn♦
yesterday
3
Alright alright, I'll go buy some rum or something too
– Tim Stone
yesterday
44
As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?
– rene
yesterday
3
@rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.
– Taryn♦
yesterday
7
Wait... will I have to... go to sleep!?
– Artemis Fowl
yesterday
6
Looking forward to the upgrade to Server 2019 in six to eight weeks.
– Michael Hampton
yesterday
4
@MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.
– Taryn♦
yesterday
16
🔺 Thanks for plenty of notice.
– Rob
yesterday
Thanks for the early notice; this will give companies using Stack Overflow Team time to plan what to do
– MilkyWay90
13 hours ago
Banner text: We're 'read only' for 60 to 80 minutes for maintenance.
– TGrif
10 hours ago
add a comment |
12
I'll cross some fingers for you :P
– Tim Stone
yesterday
5
@TimStone We need more than that. :)
– Taryn♦
yesterday
3
Alright alright, I'll go buy some rum or something too
– Tim Stone
yesterday
44
As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?
– rene
yesterday
3
@rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.
– Taryn♦
yesterday
7
Wait... will I have to... go to sleep!?
– Artemis Fowl
yesterday
6
Looking forward to the upgrade to Server 2019 in six to eight weeks.
– Michael Hampton
yesterday
4
@MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.
– Taryn♦
yesterday
16
🔺 Thanks for plenty of notice.
– Rob
yesterday
Thanks for the early notice; this will give companies using Stack Overflow Team time to plan what to do
– MilkyWay90
13 hours ago
Banner text: We're 'read only' for 60 to 80 minutes for maintenance.
– TGrif
10 hours ago
12
12
I'll cross some fingers for you :P
– Tim Stone
yesterday
I'll cross some fingers for you :P
– Tim Stone
yesterday
5
5
@TimStone We need more than that. :)
– Taryn♦
yesterday
@TimStone We need more than that. :)
– Taryn♦
yesterday
3
3
Alright alright, I'll go buy some rum or something too
– Tim Stone
yesterday
Alright alright, I'll go buy some rum or something too
– Tim Stone
yesterday
44
44
As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?
– rene
yesterday
As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?
– rene
yesterday
3
3
@rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.
– Taryn♦
yesterday
@rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.
– Taryn♦
yesterday
7
7
Wait... will I have to... go to sleep!?
– Artemis Fowl
yesterday
Wait... will I have to... go to sleep!?
– Artemis Fowl
yesterday
6
6
Looking forward to the upgrade to Server 2019 in six to eight weeks.
– Michael Hampton
yesterday
Looking forward to the upgrade to Server 2019 in six to eight weeks.
– Michael Hampton
yesterday
4
4
@MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.
– Taryn♦
yesterday
@MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.
– Taryn♦
yesterday
16
16
🔺 Thanks for plenty of notice.
– Rob
yesterday
🔺 Thanks for plenty of notice.
– Rob
yesterday
Thanks for the early notice; this will give companies using Stack Overflow Team time to plan what to do
– MilkyWay90
13 hours ago
Thanks for the early notice; this will give companies using Stack Overflow Team time to plan what to do
– MilkyWay90
13 hours ago
Banner text: We're 'read only' for 60 to 80 minutes for maintenance.
– TGrif
10 hours ago
Banner text: We're 'read only' for 60 to 80 minutes for maintenance.
– TGrif
10 hours ago
add a comment |
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
-announcements, discussion, featured
12
I'll cross some fingers for you :P
– Tim Stone
yesterday
5
@TimStone We need more than that. :)
– Taryn♦
yesterday
3
Alright alright, I'll go buy some rum or something too
– Tim Stone
yesterday
44
As you also take out chat, any chance we might be watching all of this in a live stream? Or do you expect us to go outside, get some fresh air and ... shrug talk to real people during that hour?
– rene
yesterday
3
@rene I don't think there will be a livestream this time around, unless something changes between now and maintenance day. There are a ton of moving parts and that adds another layer of stuff.
– Taryn♦
yesterday
7
Wait... will I have to... go to sleep!?
– Artemis Fowl
yesterday
6
Looking forward to the upgrade to Server 2019 in six to eight weeks.
– Michael Hampton
yesterday
4
@MichaelHampton that was the initial plan, but we ran into a lot of issues with it so decided 2016 got us the improvements we wanted on the SQL side. Also the biggest pain is leaving 2012, it wouldn’t be as complicated if we were on 2012 R2.
– Taryn♦
yesterday
16
🔺 Thanks for plenty of notice.
– Rob
yesterday
Thanks for the early notice; this will give companies using Stack Overflow Team time to plan what to do
– MilkyWay90
13 hours ago
Banner text: We're 'read only' for 60 to 80 minutes for maintenance.
– TGrif
10 hours ago