We'll be updating Provisioning API today at 1:15 pm PST. This shouldn't take longer than 15 minutes. Transformations will be resumed, your credentials will still be valid, only creating of new sandboxes in the Transformation UI will be disabled during this period.
1:30 pm PST: Migration completed. Thanks for your patience.
We're experiencing an AWS-wide DNS problem. Every 01 minute of each hour the DNS does not respond, which can cause failing attempts to connect between components in Keboola Connection. This will cause the running orchestration to fail.
It is reported all across AWS:
https://forums.aws.amazon.com/thread.jspa?threadID=161837&tstart=0
If your orchestration fails with an application error around 01 minute of an hour (it can propagate to the job a bit later, eg. at XX:02), you're most likely affected by this issue. Just re-running the orchestration will solve the problem.
Please bear with us while we're trying to solve this issue with AWS Support. Here are some examples of failed orchestrations that might help you identify this issue.
These options were turned off for VIEWs (input mappings from Redshift Storage to Redshift Transformation created as a VIEW):
These options are still present for TABLE input mappings and for MySQL Storage or Transformation.
And on the other hand we turned on Days filter for all Input mapping (was previously turned off for all Redshift transformations).
Storage bucket and tables using MySQL are now only estimating their rows count and data size (using data from SHOW TABLE STATUS query). Counting rows manually causes a full table scan and performs poorly. Redshift data is accurate.
GoodData will be performing maintenance on our hardware on Saturday, September 13th around 1pm CET (4am PST). The expected length of the maintenance window is about 5 hours. Some of our client's GoodData projects will be inaccessible at that time. We apologize in advance for any inconvenience - the maintenance is necessary in order to prevent errors in near future. We will be monitoring all data load orchestrations and will restart them as needed.
The Transformation UI now shows size of the table and backend type the bucket (mysql or redshift) in input and output mapping of a transformation.
Please note, that it does not show data transfer size, but the size of the respective tables in Storage.
Due to peak load we had to reboot the main (shared) Redshift cluster. All transformation and sandboxes are stopped and purged, data stored on this cluster is temporarily unavailable. Will be back soon so you can resume your operations.
We apologize for any inconvenience and kindly remind you, that you can have your own Redshift cluster. For more information get in touch with support@keboola.com.
We switched the Salesforce Extractor from using Salesforce API v23.0 to API v31.0. Let us know if you encounter any problems.
Part of our frontend infrastructure became inaccessible. This might have caused some orchestration failures, some UIs might not be responding (eg Orchestration UI, stuck jobs in the Writer UI). We're putting the server back online and will resume all failed orchestrations. Sorry for any inconvenience.
Update 3:30pm PST: The problem still persists.
Update 5:10pm PST: Problem resolved. All failed orchestrations were resumed.
Update 11:30pm PST: We're experiencing network connectivity issues. Some orchestrations might end up with a CURL 52, 36 or 35 errors. Feel free to retry, while we're trying to get this resolved.
Update 10:00am PST: All problems resolved, everything running OK now.
Update 5:00pm PST: We got back from AWS support: "Yesterday, we experienced an issue on our end that impacted some traffic going to any public IP address, where the source interface's MTU was above 1500. Since your instance most likely has an MTU of 9001 (Commonly default for large instances), it may have been impacted by this."
Here's a list of things that have changed in last couple weeks, in case you didn't notice in the UI directly.
Support for custom transformation or sandbox credentials was dropped in the UI. Everything in the UI is provisioned. You can still use your own credentials using the API.
When adding an input mapping in a Redshift transformation from a Redshift (Storage) backend, the engine chooses the fastest data transfer route. As the transformations and storage share the same cluster, the table never leaves the database and is transferred directly within the cluster. You have an additional option to set, if the input mapping is performed as a CREATE VIEW or CREATE TABLE from the original table. View is faster (there is no data transfer at all), but might cause memory issues, if you start piling up views on top of each other, table is slower (the data is duplicated), but may perform better on larger set of queries.
Also COPY Options pane disappeared from input mappings within Redshift, they didn't make any sense there.
Note: Be careful with mismatching datatypes.
Sandbox Credentials page now shows both MySQL and Redshift credentials with all their details.
You can now terminate both MySQL and Redshift processes.
Note: Terminating a database process is not immediate, it might take some time - there are some rollbacks on the backend.
Note: Running a Redshift transformation uses both MySQL and Redshift credentials. Terminating any of them will end the transformation.