Re: jdbc river won't start
That was it. I deleted the river using
DELETE /_river/my_river/_meta
but that was wrong, I should have used:
DELETE /_river/my_river/
Thanks!
Am Mittwoch, 11. Februar 2015 15:13:47 UTC+1 schrieb Jörg Prante:
You are sure you executed
curl -XDELETE 'localhost:9200/_river/my_river/'
before creating the new river with same name? I see there is '_version:
12', this means, you did not stop the old river instance with DELETE.
Jörg
On Wed, Feb 11, 2015 at 2:38 PM, Abid Hussain hus...@novacom.mygbiz.com
javascript: wrote:
Hi,
we are running ES on a single node cluster.
I'm facing the issue that a river is not being started after being
re-created. In detail, we first delete the index the river refers to, then
delete the river and then create it again.
*GET /_river/my_river/_meta*
{
_index: _river,
_type: my_river,
_id: _meta,
_version: 12,
found: true,
_source: {
type: jdbc,
jdbc: {
driver: com.mysql.jdbc.Driver,
url: jdbc:mysql://localhost:3306/my_db,
user: user,
password: ***,
index: my_index,
type: my_customer,
sql: SELECT * FROM my_customer
}
}
}
Unfortunately, the river is not being started after creating it. When I
request the river state it tells me that it ran last time yesterday:
{
state: [
{
name: my_river,
type: jdbc,
started: 2015-02-10T01:00:06.997Z,
last_active_begin: 2015-02-10T01:00:07.030Z,
last_active_end: 2015-02-10T01:53:34.364Z,
map: {
lastExecutionStartDate: 1423530007825,
aborted: false,
lastEndDate: 1423533216703,
counter: 1,
lastExecutionEndDate: 1423533214363,
lastStartDate: 1423530007608,
suspended: false
}
}
]
}
The connection properties didn't change since last succesful run.
In the logs is nothing said, except the message after deleting the index.
Any idea what could be the problem?
Regards,
Abid
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/5e8ffbc7-c33f-4157-b8fe-a170d38fc1fc%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/5e8ffbc7-c33f-4157-b8fe-a170d38fc1fc%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2b5be310-90cb-474a-82fd-cd233573d78c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: jdbc river won't start
You are sure you executed
curl -XDELETE 'localhost:9200/_river/my_river/'
before creating the new river with same name? I see there is '_version:
12', this means, you did not stop the old river instance with DELETE.
Jörg
On Wed, Feb 11, 2015 at 2:38 PM, Abid Hussain huss...@novacom.mygbiz.com
wrote:
Hi,
we are running ES on a single node cluster.
I'm facing the issue that a river is not being started after being
re-created. In detail, we first delete the index the river refers to, then
delete the river and then create it again.
*GET /_river/my_river/_meta*
{
_index: _river,
_type: my_river,
_id: _meta,
_version: 12,
found: true,
_source: {
type: jdbc,
jdbc: {
driver: com.mysql.jdbc.Driver,
url: jdbc:mysql://localhost:3306/my_db,
user: user,
password: ***,
index: my_index,
type: my_customer,
sql: SELECT * FROM my_customer
}
}
}
Unfortunately, the river is not being started after creating it. When I
request the river state it tells me that it ran last time yesterday:
{
state: [
{
name: my_river,
type: jdbc,
started: 2015-02-10T01:00:06.997Z,
last_active_begin: 2015-02-10T01:00:07.030Z,
last_active_end: 2015-02-10T01:53:34.364Z,
map: {
lastExecutionStartDate: 1423530007825,
aborted: false,
lastEndDate: 1423533216703,
counter: 1,
lastExecutionEndDate: 1423533214363,
lastStartDate: 1423530007608,
suspended: false
}
}
]
}
The connection properties didn't change since last succesful run.
In the logs is nothing said, except the message after deleting the index.
Any idea what could be the problem?
Regards,
Abid
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/5e8ffbc7-c33f-4157-b8fe-a170d38fc1fc%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/5e8ffbc7-c33f-4157-b8fe-a170d38fc1fc%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFXKzzVP%3DP3Og4OpUCQDVa8MNg5%2BCPpCAo-S5upy_VdSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
jdbc river won't start
Hi,
we are running ES on a single node cluster.
I'm facing the issue that a river is not being started after being
re-created. In detail, we first delete the index the river refers to, then
delete the river and then create it again.
*GET /_river/my_river/_meta*
{
_index: _river,
_type: my_river,
_id: _meta,
_version: 12,
found: true,
_source: {
type: jdbc,
jdbc: {
driver: com.mysql.jdbc.Driver,
url: jdbc:mysql://localhost:3306/my_db,
user: user,
password: ***,
index: my_index,
type: my_customer,
sql: SELECT * FROM my_customer
}
}
}
Unfortunately, the river is not being started after creating it. When I
request the river state it tells me that it ran last time yesterday:
{
state: [
{
name: my_river,
type: jdbc,
started: 2015-02-10T01:00:06.997Z,
last_active_begin: 2015-02-10T01:00:07.030Z,
last_active_end: 2015-02-10T01:53:34.364Z,
map: {
lastExecutionStartDate: 1423530007825,
aborted: false,
lastEndDate: 1423533216703,
counter: 1,
lastExecutionEndDate: 1423533214363,
lastStartDate: 1423530007608,
suspended: false
}
}
]
}
The connection properties didn't change since last succesful run.
In the logs is nothing said, except the message after deleting the index.
Any idea what could be the problem?
Regards,
Abid
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/5e8ffbc7-c33f-4157-b8fe-a170d38fc1fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
