Chrome Launches with Error: “Extension might have been corrupted and unable to connect to websocket” with Citrix UPM

Make the following modifications to UPM policy:

Files to Synchronize:

AppDataLocalGoogleChromeUserDataFirst Run

AppDataLocalGoogleChromeUserDataLocal State

AppDataLocalGoogleChromeUserDataBookmarks

AppDataLocalGoogleChromeUserDataFavicons

AppDataRoamingGoogleChromeUserDataHistory

AppDataRoamingGoogleChromeUserDataDefaultPrefrences

AppDataLocalGoogleChromeUserDataCustom Dictionary.txt

Folders to Mirror:

AppDataLocalGoogleChromeUserDataDefault

Directories to synchronize:

AppDataLocalGoogleChromeUserDataDefault

Disable profile streaming

Related:

  • No Related Posts

File Sync between HA pair ADM is broken or not working

ADM-HA file sync is broken. ADC ns.confand backup files are not synced anymore from HA1 to HA2.

HA1:

[root@ CitrixADM:/var/mps/tenants/root/ns_conf] ls -altr */ns.conf | tail -5

-rw-rw-r– 1 pgxl nobody 692153 May 12 20:43 192.168.X.x/ns.conf

-rw-rw-r– 1 pgxl nobody 4223103 May 12 21:08 192.168.X.X/ns.conf

-rw-rw-r– 1 pgxl nobody 32625 May 13 04:48 192.168.X.X/ns.conf

HA2:

[root@ CitrixADM-Sec:/var/mps/tenants/root/ns_conf] ls -altr */ns.conf | tail -5

-rw-rw-r– 1 pgxl nobody 472707 Dec 5 20:20 192.168.X.X/ns.conf

-rw-r–r– 1 pgxl nobody 472214 Dec 5 20:20 192.168.X.X/ns.conf

-rw-rw-r– 1 pgxl nobody 3853285 Dec 6 15:34 192.168.X.X/ns.conf

From mps_config.log:

Sunday, 1 Dec 19 01:32:30.958 +0000 [Error] [DeviceFilesDownload[#61]] SCP failed for: /var/mps/tenants/root/ns_conf/tmp_194.69.x.x/ns_config.tgz

Saturday, 7 Dec 19 15:45:23.265 +0000 [Debug] [ConfigScheduler[#2]] ns_conf_file_mgr::deleteNS::directory deleted: /var/mps/tenants/root/ns_conf/192.168.x.x

Saturday, 7 Dec 19 15:45:25.938 +0000 [Debug] [ConfigScheduler[#2]] ns_conf_file_mgr::deleteNS::directory deleted: /var/mps/tenants/root/ns_conf/192.168.x.x

Saturday, 7 Dec 19 15:46:12.703 +0000 [Debug] [ConfigScheduler[#2]] ns_conf_file_mgr::deleteNS::directory deleted: /var/mps/tenants/root/ns_conf/192.168.x.x

Saturday, 7 Dec 19 15:46:35.729 +0000 [Debug] [ConfigScheduler[#2]] ns_conf_file_mgr::deleteNS::directory deleted: /var/mps/tenants/root/ns_conf/192.168.x.x

Sunday, 8 Dec 19 02:31:25.018 +0000 [Error] [DeviceFilesDownload[#98]] SCP failed for: /var/mps/tenants/root/ns_conf/tmp_192.168.X.X/ns_config.tgz

Tuesday, 10 Dec 19 03:46:08.947 +0000 [Debug] [DeviceFilesDownload[#134]] execute Command Output with error dump : tar: Error opening archive: Failed to open ‘/var/mps/tenants/root/ns_conf/tmp_192.168.x.x/ns_config.tgz’

Tuesday, 10 Dec 19 03:46:08.947 +0000 [Error] [DeviceFilesDownload[#134]] ConfFileFromNS::run::untar command “tar xzf /var/mps/tenants/root/ns_conf/tmp_192.168.x.x/ns_config.tgz -C /var/mps/tenants/root/ns_conf/tmp_192.168.x.x” returned error

Related:

  • No Related Posts

ShareFile Sync for Windows isn't authenticating the user and Instead opens the Dashboard

To resolve this issue:

  1. Open regedit and navigate to: ComputerHKEY_CURRENT_USERSoftwareCitrixShareFileSync
  2. Check the registry keys for:
  • AccountID
  • CompanyName
  • Email
  • Subdomain
  • UserID
  • UserName

If the information, particularly the subdomain and Email, don’t match the user’s update them to match.(preserve the original values in case they need to be changed back).

Relaunch Sync and have the User log in again and make sure their Sync authenticate and starts syncing data.

Related:

Provisioning Users on ShareFile Using XenMobile 10 Fails

From XenMobile 10 the App Controller synchronization design has changed.

In previous versions, the App Controller used to synchronize users fetched from the Active Directory to ShareFile Cloud. This sometimes caused issue, that if a particular Role is not defined then all the users get synchronized and the ShareFile license gets exhausted.

From XenMobile 10 the synchronization is on demand. The synchronization will not occur unless the user opens the ShareFile app on the mobile. Once the user opens the ShareFile app then a synchronization will be triggered from the XenMobile server to the ShareFile cloud and the user will be synchronized.

Related:

Enterprise Sync Manager

Limitations

Requirements

Options

Once you have installed the enterprise sync tool, click Options.

Keep Sync Manager Running in Tray – Allows the esync icon to be present in the task tray even after closing the application window.

Run Scheduled Jobs Concurrently – We recommend limiting your number of jobs to five or less to avoid excessive completion times and performance issues.

Exclude File Types – Examples could include .tmp or .bak files, which are temporary or backup files that may not be needed. To enter the file types, you must include the ‘.’ (dot) with the file extension.

Error Notification Emails – You can choose to be notified when errors occur or when critical errors disable your job. An email will be sent to the email address of the user logged into the app.


Sync Jobs

  • One-Way Sync: has either a ShareFile folder or a local folder as the source, allowing you to mirror a folder in the alternate location. In this type of sync, changes made to the alternate folder will not be reflected in the source folder.
  • Two-Way Sync: automatically recognizes updates made to either folder and adopts them in the other. In the advanced settings of the enterprise sync tool, you can specify the exact schedule for individual sync jobs and set up sync with multiple ShareFile accounts and users.

To create a new sync job, click the Add button.

User-added image

1. Job Details – The job name is what you would like to call the specific job. The user name and password for the job will be your ShareFile login information (email address and password). The subdomain is the first part of your login page URL. For example: https://yourcompany.sharefile.com. Click Authenticate to verify your credentials. When you see the green check mark, proceed.

Important : If you are getting authentication issue while first time configuration, Please try to login with the same account on secure.sharefile.com and check if it works.

For the configuration we need to use the Sharefile credentials.

2. Sync Settings – Selecting Both Directions will set a two-way sync for this job. A two-way sync automatically recognizes updates made to either your ShareFile or local folder and adopts them in the other. Selecting Down will set a one-way sync from your ShareFile account to your local files. Selecting Up will set a one-way sync from your local files to your ShareFile account. Once you have selected the direction of the sync, click the blue Browse icon (to the right of the ShareFile Folder field) in order to select the folders you would like to sync. Select a ShareFile and Local folder as needed.

3.Job Schedule – You can choose to schedule the job as a Continuous, Daily, Weekly or Monthly. Depending on your choice, you may have the option of specifying an interval, either once daily or at a specific timeframe.

To complete the new job, click Create Job.

Manage Jobs

User-added image

Enable / Disable All – Stop or start all currently configured sync jobs.

Action (Turn On / Off) – Enable or disable individual sync jobs.

Reset – This action will bring the job to its original state. All files will synchronize at the next scheduled initialization of the job. ShareFile recommends utilizing the Reset function when troubleshooting a recurring issue.

Sync with a Network Path

When syncing with a network location, select the network path from My Network rather than My Computer during sync job creation.

This allows the enterprise sync tool to view the full network path (i.e. \serverfolder).


Sync with a Shared Company Drive or Similar

The following steps are recommended for advanced users. Consult the following steps when attempting to move data from a shared company drive or a similar network drive that isn’t directly connected to a computer. Note: This functionality may require additional permissions.

  1. To eliminate potential permission issues, log in to your computer as the Admin profile for the machine.
  2. Open the Services menu (Control Panel > Administrative Tools > Services).
  3. Navigate down to ShareFile Sync Service and then right click and select ‘Properties’.
  4. Choose the Log On Tab and select This Account.
  5. Log in as an administrator or your user that has permissions to read, write and execute on the network drive that you trying to sync.
  6. Once you have logged in under This Account, please stop and then restart the ShareFile SyncService under ‘Services’.
  7. Once the program has restarted, you can go in and create a new job.
  8. You will need to make sure that you use the full UNC path of folder in the network drive that you want to sync.
    1. ShareFile Enterprise Sync Manager may not be able to find the location if you give it a mapped path instead of the full UNC path.
    2. You can open the Command Prompt and use the “net use” command to find the full UNC path for your current user.
  9. If you continue to have issues after Step 8, verify that you have the read, write and execute permissions on the drive that you are trying to sync.

Manage users

Since the enterprise sync tool allows you to create jobs under different user names and ShareFile accounts, there is a section to manage users who have set up individual sync jobs. You can view all of the users with current sync jobs by clicking Manage Users.

Click the red X to delete users and their sync jobs, or you can click the settings icon to check authentication, edit password, or enable/disable current jobs.

Known Issues

Folder not found

If you receive the error message “The local folder was not found. Please restore it before re-enabling,” run the enterprise sync tool as the user on the computer where you have access to the sync jobs. To do so, please log in to the computer as an admin and click Start. From here, click Control Panel and select Administrative Tools. In the next screen, open the Services menu. Stop the ShareFile Sync service, and then right-click ShareFile Sync service and select Properties. In the screen that opens, click Log On and select This account. You can then enter the login credentials that you use to log in to the computer with access to the network. Click Apply to finish. To complete the process, start the ShareFile Sync service again and use the enterprise sync tool normally.

If you do not enter a user name to log in to your computer or if you are not sure of your full account name to enter on the Log on screen, you can use the built-in Browse feature to locate this information. This will open a new Select Users window. Click Locations on the new window and select the entire directory or network. Click OK, and then enter the first few letters of your account name in the field asking you to enter the object name to select. Next, click Check Names. This will pull up a list of the names that match your entry. You can select your user name from the list and click OK. This will fill your user name in the account field.


Intuit QuickBooks issues

Intuit QuickBooks database files are continuously in use by the QuickBooks backup software, which will not allow these items to be uploaded by the enterprise sync tool. As long as QuickBooks is running, the enterprise sync tool will not be able to upload the QuickBooks file. It may be possible to sync a QuickBooks database file, but QuickBooks must be closed completely, which requires you end to all QuickBooks processes in the Task Manager. To upload QuickBooks database files to ShareFile, log in to the web-based application or use the ShareFile Desktop Widget.


File Path Too Long

Due to Microsoft file path limitations, ShareFile enforces a file path limit of 248 characters for a given file and 260 characters for a given folder.

Use with Windows 2008 / 2012 R2 servers

While the tool may function in these environments, they are not officially supported. Consequently, ShareFile Customer Care cannot assist in troubleshooting these particular setups.

Related:

How to install and use ShareFile Sync for Mac

As of February 14, 2020 ShareFile Sync for Mac up to version 3.0 will begin deprecation.

The upgrade path is to update the tool to Citrix Files for Mac.

Please visit the Citrix Product Matrix for more information on Citrix Product Lifecycles.

Deprecation may take several weeks to complete and the tool may still be temporarily available for some users during this process.

Already installed Sync for Mac? Click here to check out the user guide!

Supported Localization: English, Spanish, German, French, Japanese, Simplified Chinese, Korean, Dutch, Russian and Portuguese.

Limitations (the following actions are not supported):

  • Syncing to a network drive
  • Creating a network drive out of a ShareFile folder
  • Mapping a folder inside the ShareFile sync folder
  • Syncing to a public folder that is shared on your network
  • Non-admin installations are currently not supported
  • ShareFile recommends adhering to a file path limit of no longer than 180 characters. Please shorten the path name by renaming its folders or in the case of Shared Folders, by only selecting the specific shared folders for synchronization instead of the root of the shared folder.

System Requirements

  • 10.10 Yosemite or later
  • High Sierra support requires Sync for Mac v 2.9.116.1 or later


Install ShareFile Sync for Mac

To download the sync tool, log in to your ShareFile account, click Apps in the navigation bar and then locate Sync for Mac. Click the Download button to download the installation file. Once the installation file has been downloaded, double-click the installation file. First, double-click the ShareFile icon to begin installation.

You will be prompted to enter the email address associated with your ShareFile account. You may also select additional folders to sync. Use the folder tree to select which files within your Personal Folders to sync. (You can modify which folders you wish to sync later in the Sync Preferences.

Note: Removing a folder from your list of synced items will move that content to your computer’s Recycle Bin.

User-added image

User-added image

Setting the sync location

To change the sync location on your Mac, access the Dashboard then select Preferences.

User-added image

Access the folder location beneath Sync Location in order to change it. Please note that in order to change the sync location, the destination you select must be an empty folder.

User-added image

Customizing sync access

Support for selective enablement of the sync tool allows you to limit access to specified users, typically those with managed or corporate devices. This feature is only available to Enterprise plans.

To use this feature with a ShareFile account that has the sync tool access set to Disabled, you must specify a custom key that is generated by your ShareFile administrator. ShareFile administrators can set this key by clicking Admin in the top navigation bar of their ShareFile account and then selecting Power Tools in the sidebar.

Under Sync, administrators can select Disabled to enter a custom 256-bit key.

On ShareFile Sync for Mac, this generated key must be added via Terminal.

To do so, run the following command, inserting the Generated Key where indicated:

  • defaults write com.citrix.sharefileFL.SFSyncEngine CustomSharedKey <EnterGeneratedKeyHere>

Additional Notes

Citrix ShareFile Sync for Mac supports StorageZones. (Restricted Zones are not supported).

This tool auto-updates. It will check for updates every day, and will only prompt for an administrator’s password when certain files that require system changes are updated. The auto-update feature can be disabled for an account by contacting ShareFile Support.


Unlink Your Account

To unlink your account, click the Unlink button in the upper right when viewing the Preferences menu.


Uninstall Sync for Mac

ShareFile recommends the following for Advanced Users. If you have a significantly large amount of data stored with your ShareFile Sync for Mac app, please consult your ShareFile Administrator prior to completely uninstalling the app.

Sync for Mac installations include an “uninstallSync.sh” file. To perform a clean uninstall of Sync for Mac:

  1. Exit Sync for Mac
  2. Run the following command in Terminal.
  • sh /Applications/ShareFile.app/Contents/uninstallSync.sh

Related:

How to Access and Use the ShareFile Sync for Windows Dashboard

Sync Dashboard

ShareFile Sync for Windows version 3.5 and later includes a Dashboard you can view from your Task Tray. To access the Dashboard menu, right-click the ShareFile icon in the Task Tray.

ShareFile Icon in the system tray

You can view currently syncing and synced files, currently checked out files, start or pause the Sync process, open your root Sync location, launch the ShareFile website in your default browser, access Sync Preferences or Exit the Sync program all from this Dashboard. You can navigate directly to a file’s location by right-clicking the file name.

To open a file in its native program, double-click the file. This requires that you have a compatible version of the file’s program installed on your machine.

Syncing in Progress

The Dashboard will also provide you with details for various errors you may encounter while syncing. Click the orange icon to access these details.

Warning message indicating a long file path error

Related:

Enterprise Sync End of Life

As of October 31, 2019 Enterprise Sync Manager Tool will begin deprecation.

Deprecation may take several weeks to complete and the tool may still be temporarily available for some users during this process.

Once complete the tool will no longer be available for users.

IMPORTANT:

Network Share Connector is an Enterprise Plan feature only.

The following alternatives for Enterprise sync are available:

If you are using ShareFile to perform a one-way sync of network drives to the cloud, we recommend migrating that data to ShareFile through the ShareFile Data Migration Tool.

If you are performing a two-way sync between ShareFile and a local drive, we recommend the following options:

  1. Migrate the Network Share data to ShareFile via the ShareFile Data Migration Tool
  2. Deploy a ShareFile Network Share Connector:
  • This will allow your users to interact directly with the Network Share from within ShareFile and Citrix Files for Mobile, Windows, or Mac.
  • Permissions are still controlled and managed directly from the Network Share.

In both options above, Citrix Files for Windows supports mapping multiple drives (mount points) to multiple folders/connectors to avoid a change in usage experience whether the data is migrated to ShareFile accessed via a ShareFile Network Share Connector.

  • Migration does not affect documents with links to a universal file path. More information can be found in this article under the heading: Mount Points.

If you are performing a one-way Sync from ShareFile to a local drive, to generate a backup of ShareFile data:

  • Customize your sync options using our PowerShell SDK / API
  • Sync your entire account, or specify users and folders to be included
  • Utilize a Citrix Ready third party, such as Qnap and SkySync.

Related:

WSS SyncAPI Data Chunk size

I need a solution

Hi,

As per the documentation:

“The client expects a 200 response code containing chunked data and an X-sync-status: more pair in the sync trailer if more data is available or X-sync-status: done if all available data was returned.”

Can anyone tell me what is the size of the chunk data when we get the reply X-sync-status: more?

I am working on an issue where I only have a limited size that I can download, and I want to stop it when the download size gets too big. 

Thank you

0

Related:

OneFS and Synchronous Writes

The last article on multi-threaded I/O generated several questions on synchronous writes in OneFS. So thought this would make a useful topic to kick off the New Year and explore in a bit more detail.

OneFS natively provides a caching mechanism for synchronous writes – or writes that require a stable write acknowledgement to be returned to a client. This functionality is known as the Endurant Cache, or EC.

The EC operates in conjunction with the OneFS write cache, or coalescer, to ingest, protect and aggregate small, synchronous NFS writes. The incoming write blocks are staged to NVRAM, ensuring the integrity of the write, even during the unlikely event of a node’s power loss. Furthermore, EC also creates multiple mirrored copies of the data, further guaranteeing protection from single node and, if desired, multiple node failures.

EC improves the latency associated with synchronous writes by reducing the time to acknowledgement back to the client. This process removes the Read-Modify-Write (R-M-W) operations from the acknowledgement latency path, while also leveraging the coalescer to optimize writes to disk. EC is also tightly coupled with OneFS’ multi-threaded I/O (Multi-writer) process, to support concurrent writes from multiple client writer threads to the same file. Plus, the design of EC ensures that the cached writes do not impact snapshot performance.

The endurant cache uses write logging to combine and protect small writes at random offsets into 8KB linear writes. To achieve this, the writes go to special mirrored files, or ‘Logstores’. The response to a stable write request can be sent once the data is committed to the logstore. Logstores can be written to by several threads from the same node, and are highly optimized to enable low-latency concurrent writes.

Note that if a write uses the EC, the coalescer must also be used. If the coalescer is disabled on a file, but EC is enabled, the coalescer will still be active with all data backed by the EC.

So what exactly does an endurant cache write sequence look like?

Say an NFS client wishes to write a file to an Isilon cluster over NFS with the O_SYNC flag set, requiring a confirmed or synchronous write acknowledgement. Here is the sequence of events that occur to facilitate a stable write.

1) A client, connected to node 3, begins the write process sending protocol level blocks.



ec_1.png



4KB is the optimal block size for the endurant cache.

2) The NFS client’s writes are temporarily stored in the write coalescer portion of node 3’s RAM. The Write Coalescer aggregates uncommitted blocks so that the OneFS can, ideally, write out full protection groups where possible, reducing latency over protocols that allow “unstable” writes. Writing to RAM has far less latency that writing directly to disk.

3) Once in the write coalescer, the endurant cache log-writer process writes mirrored copies of the data blocks in parallel to the EC Log Files.



ec_2.png

The protection level of the mirrored EC log files is the same as that of the data being written by the NFS client.

4) When the data copies are received into the EC Log Files, a stable write exists and a write acknowledgement (ACK) is returned to the NFS client confirming the stable write has occurred.



ec_3.png



The client assumes the write is completed and can close the write session.

5) The write coalescer then processes the file just like a non-EC write at this point. The write coalescer fills and is routinely flushed as required as an asynchronous write via to the block allocation manager (BAM) and the BAM safe write (BSW) path processes.

6) The file is split into 128K data stripe units (DSUs), parity protection (FEC) is calculated and FEC stripe units (FSUs) are created.



ec_4.png

7) The layout and write plan is then determined, and the stripe units are written to their corresponding nodes’ L2 Cache and NVRAM. The EC logfiles are cleared from NVRAM at this point. OneFS uses a Fast Invalid Path process to de-allocate the EC Log Files from NVRAM.



ec_5.png

8) Stripe Units are then flushed to physical disk.

9) Once written to physical disk, the data stripe Unit (DSU) and FEC stripe unit (FSU) copies created during the write are cleared from NVRAM but remain in L2 cache until flushed to make room for more recently accessed data.



ec_6.png

As far as protection goes, the number of logfile mirrors created by EC is always one more than the on-disk protection level of the file. For example:

File Protection Level

Number of EC Mirrored Copies

+1n

2

2x

3

+2n

3

+2d:1n

3

+3n

4

+3d:1n

4

+4n

5

The EC mirrors are only used if the initiator node is lost. In the unlikely event that this occurs, the participant nodes replay their EC journals and complete the writes.

If the write is an EC candidate, the data remains in the coalescer, an EC write is constructed, and the appropriate coalescer region is marked as EC. The EC write is a write into a logstore (hidden mirrored file) and the data is placed into the journal.

Assuming the journal is sufficiently empty, the write is held there (cached) and only flushed to disk when the journal is full, thereby saving additional disk activity.

An optimal workload for EC involves small-block synchronous, sequential writes – something like an audit or redo log, for example. In that case, the coalescer will accumulate a full protection group’s worth of data and be able to perform an efficient FEC write.

The happy medium is a synchronous small block type load, particularly where the I/O rate is low and the client is latency-sensitive. In this case, the latency will be reduced and, if the I/O rate is low enough, it won’t create serious pressure.

The undesirable scenario is when the cluster is already spindle-bound and the workload is such that it generates a lot of journal pressure. In this case, EC is just going to aggravate things.

So how exactly do you configure the endurant cache?

Although on by default, setting the efs.bam.ec.mode sysctl to value ‘1’ will enable the Endurant Cache:

# isi_for_array –s isi_sysctl_cluster efs.bam.ec.mode=1

EC can also be enabled & disabled per directory:

# isi set -c [on|off|endurant_all|coal_only] <directory_name>

To enable the coalescer but switch of EC, run:

# isi set -c coal_only

And to disable the endurant cache completely:

# isi_for_array –s isi_sysctl_cluster efs.bam.ec.mode=0

A return value of zero on each node from the following command will verify that EC is disabled across the cluster:

# isi_for_array –s sysctl efs.bam.ec.stats.write_blocks efs.bam.ec.stats.write_blocks: 0

If the output to this command is incrementing, EC is delivering stable writes.

As mentioned previously, EC applies to stable writes. Namely:

  • Writes with O_SYNC and/or O_DIRECT flags set
  • Files on synchronous NFS mounts

When it comes to analyzing any performance issues involving EC workloads, consider the following:

  • What changed with the workload?
  • If upgrading OneFS, did the prior version also have EC enable?
  • If the workload has moved to new cluster hardware:
  • Does the performance issue occur during periods of high CPU utilization?
  • Which part of the workload is creating a deluge of stable writes?
  • Was there a large change in spindle or node count?
  • Has the OneFS protection level changed?
  • Is the SSD strategy the same?

Disabling EC is typically done cluster-wide and this can adversely impact certain workflow elements. If the EC load is localized to a subset of the files being written, an alternative way to reduce the EC heat might be to disable the coalescer buffers for some particular target directories, which would be a more targeted adjustment. This can be configured via the isi set –c off command.

One of the more likely causes of performance degradation is from applications aggressively flushing over-writes and, as a result, generating a flurry of ‘commit’ operations. This can generate heavy read/modify/write (r-m-w) cycles, inflating the average disk queue depth, and resulting in significantly slower random reads. The isi statistics protocol CLI command output will indicate whether the ‘commit’ rate is high.

It’s worth noting that synchronous writes do not require using the NFS ‘sync’ mount option. Any programmer who is concerned with write persistence can simply specify an O_FSYNC or O_DIRECT flag on the open() operation to force synchronous write semantics for that fie handle. With Linux, writes using O_DIRECT will be separately accounted-for in the Linux ‘mountstats’ output. Although it’s almost exclusively associated with NFS, the EC code is actually protocol-agnostic. If writes are synchronous (write-through) and are either misaligned or smaller than 8KB, they have the potential to trigger EC, regardless of the protocol.

The endurant cache can provide a significant latency benefit for small (eg. 4K), random synchronous writes – albeit at a cost of some additional work for the system.

However, it’s worth bearing the following caveats in mind:

  • EC is not intended for more general purpose I/O.
  • There is a finite amount of EC available. As load increases, EC can potentially ‘fall behind’ and end up being a bottleneck.
  • Endurant Cache does not improve read performance, since it’s strictly part of the write process.
  • EC will not increase performance of asynchronous writes – only synchronous writes.

Related: