[
https://issues.apache.org/jira/browse/FLINK-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265138#comment-16265138
]
ASF GitHub Bot commented on FLINK-5465:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5058
I would like to make a few comments for followup:
- I think `TimerServiceOptions` should not be an own class, we are
getting a crazy fragmentation of options into classes (that have sometimes,
like here, only one option defined). Let's merge these into the
`TaskManagerOptions`.
- The config key does not reflect the scheme in which all other config
keys are defined. It reads like a name where the dot '.' is a work separator.
The scheme in which all other config keys are defined is hierarchical, like a
path in a nested config group/object structure. Think that the configuration is
one huge JSON object, and the key is the dot path to the entry. Hence a key
like `taskmanager.timers.shutdown-timeout` (or
`taskmanager.timers.shutdown.timeout`, if we view `shutdown` as a full config
group/object) would be in line with the resulting style.
> RocksDB fails with segfault while calling AbstractRocksDBState.clear()
> ----------------------------------------------------------------------
>
> Key: FLINK-5465
> URL: https://issues.apache.org/jira/browse/FLINK-5465
> Project: Flink
> Issue Type: Bug
> Components: State Backends, Checkpointing
> Affects Versions: 1.2.0
> Reporter: Robert Metzger
> Assignee: Stefan Richter
> Fix For: 1.4.0, 1.5.0
>
> Attachments: hs-err-pid26662.log
>
>
> I'm using Flink 699f4b0.
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f91a0d49b78, pid=26662, tid=140263356024576
> #
> # JRE version: Java(TM) SE Runtime Environment (7.0_67-b01) (build
> 1.7.0_67-b01)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.65-b04 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # C [librocksdbjni-linux64.so+0x1aeb78]
> rocksdb::GetColumnFamilyID(rocksdb::ColumnFamilyHandle*)+0x8
> #
> # Failed to write core dump. Core dumps have been disabled. To enable core
> dumping, try "ulimit -c unlimited" before starting Java again
> #
> # An error report file with more information is saved as:
> #
> /yarn/nm/usercache/robert/appcache/application_1484132267957_0007/container_1484132267957_0007_01_000010/hs_err_pid26662.log
> Compiled method (nm) 1869778 903 n org.rocksdb.RocksDB::remove
> (native)
> total in heap [0x00007f91b40b9dd0,0x00007f91b40ba150] = 896
> relocation [0x00007f91b40b9ef0,0x00007f91b40b9f48] = 88
> main code [0x00007f91b40b9f60,0x00007f91b40ba150] = 496
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.sun.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
