Skip to Main Content
Spotfire Ideas Portal
Status Future Consideration
Product Spotfire
Categories Installation
Created by Guest
Created on Jan 9, 2020

New server hotfix installation process

We have noticed the change you made of patching the server from Hotfixes to now applying Service Packs. These Service Packs installation basically equates to an upgrade. So, the patching of our infrastructure went from being a simple process with minimal intervention of other teams to a complex process (like any other upgrades) where we have to  involve DBA team, infrastructure team, and business owners. We also have to do more testing. In our case, we have several hundred unique users per day and an event like this has a big impact on productivity. I don't really know what the rational behind this change is and what is the trade off if any. In our case, this complexity, increases our maintenance cost. I have the feeling we are not the only ones having this issue. For this reason, it would be nice if you can find a simpler way to maintain the server without having to upgrade and change versions constantly

  • Attach files
  • Admin
    Miguel Díez
    Feb 7, 2020


    I understand your concern.

    The rational behind is that we believe we will be most likely moving into an scenario with continuous upgrades. At the same time, we are making big efforts to simplify and automate the upgrade process.

    I would like to hear from you guys what parts of the upgrade process do require the most effort (i.e. validation ?) for your organization. I'll send separated invitations.


  • Guest
    Jan 29, 2020

    I completely agree with this and have raised through Product Management. Prior to the change we could run automated scripts that applied hotfixes to our servers without any downtime and very little visibility to our users (we have tens of thousands). With the new approach we're expected to take down our entire environment  (even if only briefly), particularly since the Apache Ignite software is updated in each service pack (which means you can't run a mixed version cluster even if you wanted to).