Service Fabric

Do you have an idea, suggestion, or feedback based on your experience with Azure Service Fabric? We would love to hear from you.

Please take a few minutes to submit your feedback in one of the forums available on the right or vote up an idea submitted by another Azure Service Fabric customer. All the feedback shared in these forums are being monitored and reviewed by the Microsoft Azure Service Fabric team.

Please remember this forum is for Azure Service Fabric, and if you have feedback on other Microsoft products, services or platforms, please submit your feedback in the appropriate forum (found on the right hand side).

Thanks for your feedback – we look forward to improving your satisfaction with Azure Service Fabric

  1. Fix Disk Space Usage

    Create a setting that will allow users to toggle how many or how long to keep log/trace files. They are growing out of control and taking up gigabytes of space.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add chaos testing capabilities to the Service Fabric Explorer

    Having the possibility to start basic integrated chaos testing from within the Service Fabric Explorer without having to write any lines of code.

    Feasible ideas would be to shutdown random nodes to see how your system reacts to it.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Be able to add node types after deployment

    When wanting to add new nodetypes to a cluster after deployment either updating the arm template or making the put calls to the provider with new node types the error

    {
    "error": {

    "code": "ManualScaleUpOrDownNotAllowed",
    
    "message": "VMInstance count cannot be modified."

    }
    }

    is returned. The count is not changed for any of the existing nodes,so the error is also a bit misleading.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Custom Actor's Queue Extesibility

    Custom Actor's Queue Extensibility

    the Actor's message queuing is one of the model's fundamentals

    Exposing extensibility point for Actor's queue replacement
    will allow to developers to address scenario that may not supported on
    the current Actor queuing model.

    developers can use it to alter the queue strategy using
    Azure Service Bus or Azure Queue.

    by doing so the queue will become reliable for cluster crash
    or mistakable deployment (without upgrade)

    the current implementation rely on WCF which may
    make it relative easy by replacing the WCF transport channel
    (similar to the Net MSMQ binding)

    the Actor class can use virtual…

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow multiple configurations of the same service

    We have services that are abstracted well enough that, if the ApplicationManifest allowed it, we could configure the same service with different ConfigOverrides (potentially having different instance/partition counts of each configuration) to handle different workloads. It seems the only way we can accomplish this is to essentially duplicate the entire service with a different name (yes, they can be mostly shared code via a library assembly, but this is more cumbersome than it needs to be) so that it can be imported/configured separately.

    Here is a suggestion that maybe helps illustrate what I am asking for: Suppose that in the…

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Application Parameters Override in VSTS Deploy Task

    The Azure Resource Group Deployment Task in Visual Studio Team Services (VSTS) has a nice Override parameters feature.

    Add a similar parameter called "Application parameter override" to the Service Fabric Application Deployment task for VSTS.

    With the recent additions in VSTS to link Key Vaults to Variable Groups and to scope VSTS Release variables per environment, it becomes more and more common to use VSTS variables for app param overrides.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Show current service fabric version on Cluster Essential Page.

    It would be really helpful to see the version of the current Service Fabric version on the Essential Page of the Explorer page.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Security Groups for Service Fabric Explorer

    For multiple teams that would share Service Fabric clusters it would be nice to set security groups for the applications. This would not allow another team to create and delete another application

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Rebalance partitions for stateful services and actors when adding nodes

    Currently, you cannot change the partitioning of a stateful service/actor. I'm forced to anticipate future horizontal scale and create that many partitions, so that when nodes are added to the cluster, load is moved off of hot nodes to the new ones.

    NoSQL databases, such as MongoDB, rebalance the partitions when adding a node. If I"m doing a range partition and have 5 nodes, the range is sliced up into 5 equal(ish) shards. If I add node later, data is migrated until I have 6 equal(ish) shards.

    Having this functionality in Service Fabric for stateful services/actors would allow better horizontal…

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Stop VMs

    Need the ability to shut down a cluster's VM's to save cost when not in use. For a development/QA environment, it'd make sense to be able to deprovision VM's to save on cost

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Singleton actor-like compute units

    I can see a use for both stateful and stateless units of business logic that are similar to actors, but singletons. I'll call these Units. These would be accessible to clients, Actors and other Units and would be used in a similar way. Some simple examples:

    Stateless:
    var dateProvider = UnitProxy.Create<DateProviderUnit>();
    var date = dateProvider.NowAsync();

    Stateful:
    var idProvider = UnitProxy.Create<IdProviderUnit>();
    var id = idProvider.NextAsync();

    This can be emulated at the moment by using Actors, and using Create with a known ActorId to access the same instance.

    The benefit of making them a 'first class citizen' is that the code would…

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add process id/thread id in details of partition, replica view in explorer

    Add process id/thread id in details of partition, replica view in explorer so that it helps in debugging and also allow taking dump

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow a single machine cluster configuration

    Please remove the requirement of having a cluster of 3 machines on-premise. Some of our clients do not have the need for scaling or reliability. They just want one machine just like a developer has a local cluster to test. It's for deployment to smaller customers of our product.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Establish a (persistent) relationship between Actors

    There are several master/detail type scenarios where it would be helpful to have a one-to-many or many-to-many relationship between stateful actors. In the sample and documentation this kind of relationship is established by storing lists of IDs inside the actor state. This works for tens or hundreds of IDs but when you get to thousands or millions it breaks down.

    It would be very useful to have a first-class mechanism for relating actors together and persisting that relationship (presumably in an underlying reliable collection).

    If such a relationship existed an actor could enumerate all of its related actors. There might…

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add service management options to fabric explorer

    The current context options in the SF Explorer allows deployment and deletion of Application and Services, as well as manage Nodes (pause, restart...)

    I would like the option to control the deployed services more explicitly like restarting a service and be able to start and stop them (without SF trying to restart them). This would be very usefull during development.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Make available in UK regions

    Now that we've got UK West and UK South regions, when can we expect to see Service Fabric made available there? As it stands I'm going to have to stick with North & West Europe for my service.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. FabActUtil.exe needs to give failure messages

    By far the single most frustrating part of Service Fabric development is FabActUtil.exe returning -1 for every single solitary error at compile time. It gives no indication whatsoever of what went wrong.

    We have burned extensive hours (and even examined the EXE's code with Reflector) just to try to get the slightest hint of what has gone wrong.

    Sometimes it works locally but fails on the build server. Sometimes it works on one dev's machine and not another. Sometimes it fails on compile and then when immediately recompiling it works.

    Often, we figure out what is causing the failure and…

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Remoting Communication with Node.JS

    It should be possible to run a service on Node.JS which can communicate with C# services using the remoting communication channel. It should be possible to do both-way communication and a ServiceProxy implementation for Node.JS that allows for easy service URI discovery.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Python SDK & Samples

    Support for Python within the templates would be phenominal.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow to choose a folder when adding a new service fabric service

    Please consider to extend the "Add New Service Fabric Service" dialog in visual studio with the option to choose a target folder.

    While the "add New Project" dialog has this ability for good reasons, the add-new-service-fabric-service lacks this setting.
    i guess the desire to not only structure projects in project-explorer, but also structure projects on the file-system-level in a meaningful way is understandable. we want to have all service-fabric-service-projects grouped in a folder below the solution-folder.

    now our problem is, when adding another service-fabric-service to this service-fabric-project, we can not choose in which subfolder it should be created, but instead…

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Service Fabric

Categories

Feedback and Knowledge Base