You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by aljoscha <gi...@git.apache.org> on 2016/04/04 16:58:27 UTC
[GitHub] flink pull request: [FLINK-3654] Disable Write-Ahead-Log in RocksD...
GitHub user aljoscha opened a pull request:
https://github.com/apache/flink/pull/1850
[FLINK-3654] Disable Write-Ahead-Log in RocksDB State
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aljoscha/flink rocksdb-no-wal
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1850.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1850
----
commit 0580de64ac36bd73f505084ffac44e512f127da2
Author: Aljoscha Krettek <al...@gmail.com>
Date: 2016-03-22T17:08:15Z
[FLINK-3654] Disable Write-Ahead-Log in RocksDB State
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] flink pull request: [FLINK-3654] Disable Write-Ahead-Log in RocksD...
Posted by aljoscha <gi...@git.apache.org>.
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1850#issuecomment-205406051
done :smile:
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] flink pull request: [FLINK-3654] Disable Write-Ahead-Log in RocksD...
Posted by aljoscha <gi...@git.apache.org>.
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1850#issuecomment-205398515
I'm seeing this failure on Travis: https://travis-ci.org/aljoscha/flink/jobs/120638971
Could be a bug introduced by the change. I'm investigating...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] flink pull request: [FLINK-3654] Disable Write-Ahead-Log in RocksD...
Posted by aljoscha <gi...@git.apache.org>.
Github user aljoscha closed the pull request at:
https://github.com/apache/flink/pull/1850
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] flink pull request: [FLINK-3654] Disable Write-Ahead-Log in RocksD...
Posted by uce <gi...@git.apache.org>.
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/1850#issuecomment-205359909
Should we add this for `1.0.2` (or `1.0.1` if the RC gets cancelled)?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] flink pull request: [FLINK-3654] Disable Write-Ahead-Log in RocksD...
Posted by aljoscha <gi...@git.apache.org>.
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1850#issuecomment-206259647
I think we have a winner now. I changed the backup options to not back up the WAL. This seems to have been the problem. Only logical since there is no WAL anymore...
Before, 2 out of 5 travis runs (i.e. 5*5) would have errors. Now all 5 runs that I started were successful.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] flink pull request: [FLINK-3654] Disable Write-Ahead-Log in RocksD...
Posted by aljoscha <gi...@git.apache.org>.
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1850#issuecomment-206799977
Manually merged
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] flink pull request: [FLINK-3654] Disable Write-Ahead-Log in RocksD...
Posted by uce <gi...@git.apache.org>.
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/1850#issuecomment-205402626
Would you mind triggering a few builds over night?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] flink pull request: [FLINK-3654] Disable Write-Ahead-Log in RocksD...
Posted by aljoscha <gi...@git.apache.org>.
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1850#issuecomment-205391579
Can do, yes. But we shouldn't block, as you said.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---