[jira] [Comment Edited] (KAFKA-3805) Java_org_rocksdb_RocksDB_write error
[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320525#comment-15320525 ] Andres Gomez Ferrer edited comment on KAFKA-3805 at 6/8/16 1:26 PM: [~ijuma] yeah, this is a possibility. But .. when the partitions are rebalanced the cache always are rebalanced, isn't? for example: If I have 4 partitions and to the same application id (kafka-streams-7778), I have some like this on my filesystem: root@ubuntu:~# ls /tmp/kafka-streams/kafka-streams-7778/ 0_0 0_1 0_2 0_3 And I suppose that when I will launch another Kafka stream application the partitions will be rebalanced and one application write inside [0_0 0_1] and the another on [0_2 0_3], isn't? was (Author: agomez): [~ijuma] yeah, this is a possibility > Java_org_rocksdb_RocksDB_write error > > > Key: KAFKA-3805 > URL: https://issues.apache.org/jira/browse/KAFKA-3805 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.0.0 > Environment: * Ubuntu Server 16.04 LTS > - Java: OpenJDK Runtime Environment (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > * OSX 10.11.5 >- Java: Java(TM) SE Runtime Environment (build 1.8.0_74-b02) >Reporter: Andres Gomez Ferrer >Assignee: Guozhang Wang >Priority: Critical > Attachments: hs_err_pid23047.log > > > I reproduce the error working with simple two instances of my kafka streams > application reading from one topic writing on other and using a RocksDB store. > I reproduce it starting one instance, sending some messages on the input > topic and later starting another Kafka streams instance. Then, the first > instance died and drop a core dump. > -- > A fatal error has been detected by the Java Runtime Environment: > SIGSEGV (0xb) at pc=0x7f9f488fd8e8, pid=23047, tid=140322171361024 > JRE version: OpenJDK Runtime Environment (8.0_91-b14) (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > Java VM: OpenJDK 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 > compressed oops) > Problematic frame: > C [librocksdbjni712288404493406713..so+0x15b8e8] > Java_org_rocksdb_RocksDB_write0+0x48 > Core dump written. Default location: /root/core or core.23047 > An error report file with more information is saved as: > /root/hs_err_pid23047.log > If you would like to submit a bug report, please visit: >http://bugreport.java.com/bugreport/crash.jsp > The crash happened outside the Java Virtual Machine in native code. > See problematic frame for where to report the bug. > -- > The core dump is there: > https://s3-eu-west-1.amazonaws.com/arodriguezg-test/core > Note: The core dump is collected at Ubuntu Server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KAFKA-3805) Java_org_rocksdb_RocksDB_write error
[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320525#comment-15320525 ] Andres Gomez Ferrer edited comment on KAFKA-3805 at 6/8/16 1:18 PM: [~ijuma] yeah, this is a possibility was (Author: agomez): [~ijuma]yeah, this is a possibility > Java_org_rocksdb_RocksDB_write error > > > Key: KAFKA-3805 > URL: https://issues.apache.org/jira/browse/KAFKA-3805 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.0.0 > Environment: * Ubuntu Server 16.04 LTS > - Java: OpenJDK Runtime Environment (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > * OSX 10.11.5 >- Java: Java(TM) SE Runtime Environment (build 1.8.0_74-b02) >Reporter: Andres Gomez Ferrer >Assignee: Guozhang Wang >Priority: Critical > Attachments: hs_err_pid23047.log > > > I reproduce the error working with simple two instances of my kafka streams > application reading from one topic writing on other and using a RocksDB store. > I reproduce it starting one instance, sending some messages on the input > topic and later starting another Kafka streams instance. Then, the first > instance died and drop a core dump. > -- > A fatal error has been detected by the Java Runtime Environment: > SIGSEGV (0xb) at pc=0x7f9f488fd8e8, pid=23047, tid=140322171361024 > JRE version: OpenJDK Runtime Environment (8.0_91-b14) (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > Java VM: OpenJDK 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 > compressed oops) > Problematic frame: > C [librocksdbjni712288404493406713..so+0x15b8e8] > Java_org_rocksdb_RocksDB_write0+0x48 > Core dump written. Default location: /root/core or core.23047 > An error report file with more information is saved as: > /root/hs_err_pid23047.log > If you would like to submit a bug report, please visit: >http://bugreport.java.com/bugreport/crash.jsp > The crash happened outside the Java Virtual Machine in native code. > See problematic frame for where to report the bug. > -- > The core dump is there: > https://s3-eu-west-1.amazonaws.com/arodriguezg-test/core > Note: The core dump is collected at Ubuntu Server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KAFKA-3805) Java_org_rocksdb_RocksDB_write error
[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320507#comment-15320507 ] Andres Gomez Ferrer edited comment on KAFKA-3805 at 6/8/16 1:09 PM: [~enothereska] I use the same application id, because I want that the two instances balance the Kafka topics partitions. In the docs: application.id - An identifier for the stream processing application. Must be unique within the Kafka cluster. It is used as 1) the default client-id prefix, 2) the group-id for membership management, 3) the changelog topic prefix. The number 2) told that the application id is used to make the group-id and it must be the same if I want that the two instances balance the topic partitions, isn't?? I think that, if I use differents applications id both Kafka stream applications process all messages from all partitions. was (Author: agomez): [~enothereska] I use the same application id, because I want that the two instances balance the Kafka topics partitions. In the docs: application.id - An identifier for the stream processing application. Must be unique within the Kafka cluster. It is used as 1) the default client-id prefix, 2) the group-id for membership management, 3) the changelog topic prefix. The number 2) told that the application id is used to make the group-id and it must be the same if I want that the two instances balance the topic partitions, isn't?? I think that, if I use differents applications id both Kafka stream applications read all messages from all partitions. > Java_org_rocksdb_RocksDB_write error > > > Key: KAFKA-3805 > URL: https://issues.apache.org/jira/browse/KAFKA-3805 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.0.0 > Environment: * Ubuntu Server 16.04 LTS > - Java: OpenJDK Runtime Environment (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > * OSX 10.11.5 >- Java: Java(TM) SE Runtime Environment (build 1.8.0_74-b02) >Reporter: Andres Gomez Ferrer >Assignee: Guozhang Wang >Priority: Critical > Attachments: hs_err_pid23047.log > > > I reproduce the error working with simple two instances of my kafka streams > application reading from one topic writing on other and using a RocksDB store. > I reproduce it starting one instance, sending some messages on the input > topic and later starting another Kafka streams instance. Then, the first > instance died and drop a core dump. > -- > A fatal error has been detected by the Java Runtime Environment: > SIGSEGV (0xb) at pc=0x7f9f488fd8e8, pid=23047, tid=140322171361024 > JRE version: OpenJDK Runtime Environment (8.0_91-b14) (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > Java VM: OpenJDK 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 > compressed oops) > Problematic frame: > C [librocksdbjni712288404493406713..so+0x15b8e8] > Java_org_rocksdb_RocksDB_write0+0x48 > Core dump written. Default location: /root/core or core.23047 > An error report file with more information is saved as: > /root/hs_err_pid23047.log > If you would like to submit a bug report, please visit: >http://bugreport.java.com/bugreport/crash.jsp > The crash happened outside the Java Virtual Machine in native code. > See problematic frame for where to report the bug. > -- > The core dump is there: > https://s3-eu-west-1.amazonaws.com/arodriguezg-test/core > Note: The core dump is collected at Ubuntu Server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KAFKA-3805) Java_org_rocksdb_RocksDB_write error
[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320507#comment-15320507 ] Andres Gomez Ferrer edited comment on KAFKA-3805 at 6/8/16 1:04 PM: [~enothereska] I use the same application id, because I want that the two instances balance the Kafka topics partitions. In the docs: application.id - An identifier for the stream processing application. Must be unique within the Kafka cluster. It is used as 1) the default client-id prefix, 2) the group-id for membership management, 3) the changelog topic prefix. The number 2) told that the application id is used to make the group-id and it must be the same if I want that the two instances balance the topic partitions, isn't?? I think that, if I use differents applications id both Kafka stream applications read all messages from all partitions. was (Author: agomez): I use the same application id, because I want that the two instances balance the Kafka topics partitions. In the docs: application.id - An identifier for the stream processing application. Must be unique within the Kafka cluster. It is used as 1) the default client-id prefix, 2) the group-id for membership management, 3) the changelog topic prefix. The number 2) told that the application id is used to make the group-id and it must be the same if I want that the two instances balance the topic partitions, isn't?? I think that, if I use differents applications id both Kafka stream applications read all messages from all partitions. > Java_org_rocksdb_RocksDB_write error > > > Key: KAFKA-3805 > URL: https://issues.apache.org/jira/browse/KAFKA-3805 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.0.0 > Environment: * Ubuntu Server 16.04 LTS > - Java: OpenJDK Runtime Environment (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > * OSX 10.11.5 >- Java: Java(TM) SE Runtime Environment (build 1.8.0_74-b02) >Reporter: Andres Gomez Ferrer >Assignee: Guozhang Wang >Priority: Critical > Attachments: hs_err_pid23047.log > > > I reproduce the error working with simple two instances of my kafka streams > application reading from one topic writing on other and using a RocksDB store. > I reproduce it starting one instance, sending some messages on the input > topic and later starting another Kafka streams instance. Then, the first > instance died and drop a core dump. > -- > A fatal error has been detected by the Java Runtime Environment: > SIGSEGV (0xb) at pc=0x7f9f488fd8e8, pid=23047, tid=140322171361024 > JRE version: OpenJDK Runtime Environment (8.0_91-b14) (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > Java VM: OpenJDK 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 > compressed oops) > Problematic frame: > C [librocksdbjni712288404493406713..so+0x15b8e8] > Java_org_rocksdb_RocksDB_write0+0x48 > Core dump written. Default location: /root/core or core.23047 > An error report file with more information is saved as: > /root/hs_err_pid23047.log > If you would like to submit a bug report, please visit: >http://bugreport.java.com/bugreport/crash.jsp > The crash happened outside the Java Virtual Machine in native code. > See problematic frame for where to report the bug. > -- > The core dump is there: > https://s3-eu-west-1.amazonaws.com/arodriguezg-test/core > Note: The core dump is collected at Ubuntu Server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KAFKA-3805) Java_org_rocksdb_RocksDB_write error
[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320400#comment-15320400 ] Andres Gomez Ferrer edited comment on KAFKA-3805 at 6/8/16 11:49 AM: - Yes, I started another Kafka Streams on the same machine. Is this a problem??? I put two environments because I reproduce the problem in both. was (Author: agomez): Yes, I started another Kafka Streams in the same machine. Is this a problem??? > Java_org_rocksdb_RocksDB_write error > > > Key: KAFKA-3805 > URL: https://issues.apache.org/jira/browse/KAFKA-3805 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.0.0 > Environment: * Ubuntu Server 16.04 LTS > - Java: OpenJDK Runtime Environment (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > * OSX 10.11.5 >- Java: Java(TM) SE Runtime Environment (build 1.8.0_74-b02) >Reporter: Andres Gomez Ferrer >Assignee: Guozhang Wang >Priority: Critical > Attachments: hs_err_pid23047.log > > > I reproduce the error working with simple two instances of my kafka streams > application reading from one topic writing on other and using a RocksDB store. > I reproduce it starting one instance, sending some messages on the input > topic and later starting another Kafka streams instance. Then, the first > instance died and drop a core dump. > -- > A fatal error has been detected by the Java Runtime Environment: > SIGSEGV (0xb) at pc=0x7f9f488fd8e8, pid=23047, tid=140322171361024 > JRE version: OpenJDK Runtime Environment (8.0_91-b14) (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > Java VM: OpenJDK 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 > compressed oops) > Problematic frame: > C [librocksdbjni712288404493406713..so+0x15b8e8] > Java_org_rocksdb_RocksDB_write0+0x48 > Core dump written. Default location: /root/core or core.23047 > An error report file with more information is saved as: > /root/hs_err_pid23047.log > If you would like to submit a bug report, please visit: >http://bugreport.java.com/bugreport/crash.jsp > The crash happened outside the Java Virtual Machine in native code. > See problematic frame for where to report the bug. > -- > The core dump is there: > https://s3-eu-west-1.amazonaws.com/arodriguezg-test/core > Note: The core dump is collected at Ubuntu Server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KAFKA-3805) Java_org_rocksdb_RocksDB_write error
[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320400#comment-15320400 ] Andres Gomez Ferrer edited comment on KAFKA-3805 at 6/8/16 11:49 AM: - Yes, I started another Kafka Streams on the same machine. Is this a problem??? I put two environments because I have reproduced the problem in both. was (Author: agomez): Yes, I started another Kafka Streams on the same machine. Is this a problem??? I put two environments because I reproduce the problem in both. > Java_org_rocksdb_RocksDB_write error > > > Key: KAFKA-3805 > URL: https://issues.apache.org/jira/browse/KAFKA-3805 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.0.0 > Environment: * Ubuntu Server 16.04 LTS > - Java: OpenJDK Runtime Environment (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > * OSX 10.11.5 >- Java: Java(TM) SE Runtime Environment (build 1.8.0_74-b02) >Reporter: Andres Gomez Ferrer >Assignee: Guozhang Wang >Priority: Critical > Attachments: hs_err_pid23047.log > > > I reproduce the error working with simple two instances of my kafka streams > application reading from one topic writing on other and using a RocksDB store. > I reproduce it starting one instance, sending some messages on the input > topic and later starting another Kafka streams instance. Then, the first > instance died and drop a core dump. > -- > A fatal error has been detected by the Java Runtime Environment: > SIGSEGV (0xb) at pc=0x7f9f488fd8e8, pid=23047, tid=140322171361024 > JRE version: OpenJDK Runtime Environment (8.0_91-b14) (build > 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14) > Java VM: OpenJDK 64-Bit Server VM (25.91-b14 mixed mode linux-amd64 > compressed oops) > Problematic frame: > C [librocksdbjni712288404493406713..so+0x15b8e8] > Java_org_rocksdb_RocksDB_write0+0x48 > Core dump written. Default location: /root/core or core.23047 > An error report file with more information is saved as: > /root/hs_err_pid23047.log > If you would like to submit a bug report, please visit: >http://bugreport.java.com/bugreport/crash.jsp > The crash happened outside the Java Virtual Machine in native code. > See problematic frame for where to report the bug. > -- > The core dump is there: > https://s3-eu-west-1.amazonaws.com/arodriguezg-test/core > Note: The core dump is collected at Ubuntu Server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
