Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 06:50
    alvin-su commented #472
  • 03:15
    fengrui358 starred exceptionless/Exceptionless
  • Dec 15 14:07
    niemyjski commented #472
  • Dec 15 07:50
    alvin-su opened #472
  • Dec 15 01:35
    niemyjski synchronize #452
  • Dec 15 01:35

    niemyjski on elastic7

    Only put consumes attribute on … (compare)

  • Dec 14 16:39
    ejsmith synchronize #452
  • Dec 14 16:39

    ejsmith on elastic7

    Log the correct task id and cat… (compare)

  • Dec 14 06:25
    ejsmith synchronize #452
  • Dec 14 06:25

    ejsmith on elastic7

    Minor (compare)

  • Dec 14 06:00
    ejsmith synchronize #452
  • Dec 14 06:00

    ejsmith on elastic7

    Add missing task id (compare)

  • Dec 13 22:43
    ejsmith synchronize #452
  • Dec 13 22:43

    ejsmith on elastic7

    More reindex job changes (compare)

  • Dec 13 15:46
    ejsmith synchronize #452
  • Dec 13 15:46

    ejsmith on elastic7

    Just retry 3 times (compare)

  • Dec 13 15:44
    ejsmith synchronize #452
  • Dec 13 15:44

    ejsmith on elastic7

    More log message changes (compare)

  • Dec 13 14:25
    niemyjski synchronize #452
Blake Niemyjski
@niemyjski
it will show you all the indexs / records
Lukas Wöhrl
@woehrl01
looks, good, I have >8000 stacks-v1 about the same count like in mongodb
Blake Niemyjski
@niemyjski
ok
so looks like those were migrated
now just need to migrate events
how many errors do you have?
Lukas Wöhrl
@woehrl01
none, inside of elastic
Blake Niemyjski
@niemyjski
yes but in mongo
Lukas Wöhrl
@woehrl01
about 46k
Blake Niemyjski
@niemyjski
ok
that should be a pretty quick migration
you should just have to queue them
and them run the migration job
Lukas Wöhrl
@woehrl01
it is just queueing from today
Blake Niemyjski
@niemyjski
2015-06-11 17:14:32.8579|INFO|EventMigrationJob|Processing event migration jobs
for date range: 2014-07-31T00:00:00.0000000+00:00-2014-07-31T12:00:00.0000000+00:00
Lukas Wöhrl
@woehrl01
aaaaah, i see , i have to run the last one with -c
Blake Niemyjski
@niemyjski
it looks like it started queueing from 11m ago
ahh yeah
Lukas Wöhrl
@woehrl01
:D
Blake Niemyjski
@niemyjski
sorry :)
my bad
lol
Lukas Wöhrl
@woehrl01
thank you very much!
Blake Niemyjski
@niemyjski
np
Lukas Wöhrl
@woehrl01
now they are flooding in
thanks a lot for your help! and a great piece of software!
Blake Niemyjski
@niemyjski
the ui won't refresh for these events
coming in
due to there would be thousands / millions of notifications for it
but once it's done any events submitted via teh normal api will refesh the ui
was it pretty easy to setup the 2.0 project?
thanks :D
tell your friends about us :D
Lukas Wöhrl
@woehrl01
It took some time to figure out that I need to elasticsearch.yml from the repo
but the hardest part is the migration ;)
it would be nice, if there is a .bat to start this part
Blake Niemyjski
@niemyjski
yeah
if you want to send me all the commands you used
I'll create a gist for it
we are going to move towards a wiki on github and we can add that there
Lukas Wöhrl
@woehrl01
and of course that you need redis
Blake Niemyjski
@niemyjski
yeah didn't think of that until you ran into that
normally if you have a single node you don't need it
Lukas Wöhrl
@woehrl01
that's the reason, I disabled it first ;)
Blake Niemyjski
@niemyjski
but you do when you queue events for migration (due to multiprocess)
Lukas Wöhrl
@woehrl01
for the gist, it's just the three statements you provided + "-c" on the last one
Blake Niemyjski
@niemyjski
if you have it setup, I'd probably still use it due to it being more reliable to process restarts
you don't lose any queued data on reboot
yeah
Lukas Wöhrl
@woehrl01
yep, I think I will keep it