1
00:00:01,110 --> 00:00:03,700
We're going to start working on our ticket service again very shortly.

2
00:00:03,720 --> 00:00:09,670
But before we do just a quick reminder if we go back over to our terminal right now and do a cube CDL

3
00:00:09,690 --> 00:00:14,790
get pods we will see that we've got our Nats deployment or the Nats pod running right there.

4
00:00:14,790 --> 00:00:20,220
Now we've been running a lot of test code and we've been emitting a ton of events over to that Nats

5
00:00:20,310 --> 00:00:24,360
deployment that probably have a lot of trash data inside them.

6
00:00:24,360 --> 00:00:29,880
So we had a ton of events like for me I think I had at least 90 all concerned with that ticket update

7
00:00:29,940 --> 00:00:34,590
events or the ticket Create Event whichever it was and chances are we might have been emitting some

8
00:00:34,590 --> 00:00:36,450
data that wasn't really valid.

9
00:00:36,450 --> 00:00:42,000
I know for certain of we had an idea inside that ticket create event of like one two 3 and that is definitely

10
00:00:42,000 --> 00:00:47,460
not a valid ticket I.D. so it might make a lot of sense for us to restart this Nat spot right here which

11
00:00:47,460 --> 00:00:51,840
will cause all the events that we have already emitted to be dumped.

12
00:00:51,840 --> 00:00:55,860
Remember that Nats by default stores all these events in memory.

13
00:00:55,890 --> 00:01:00,390
So if we just restart the thing all the events we've emitted so far get completely dumped and we won't

14
00:01:00,480 --> 00:01:04,470
have to worry about consuming those kind of non valid events.

15
00:01:04,470 --> 00:01:09,750
Once we start to handle incoming ticket created events where once we create a real publisher inside

16
00:01:09,750 --> 00:01:11,130
of one of our services.

17
00:01:11,190 --> 00:01:17,160
Long story short let's just restart that thing so I to find a listing I'm going to copy the name and

18
00:01:17,160 --> 00:01:24,570
I'll do a cube Seitel delete pod and then put in the name that's going to delete the pod.

19
00:01:24,630 --> 00:01:30,030
The deployment is going to automatically detect that the pod has been deleted and start up a new version.

20
00:01:30,030 --> 00:01:31,590
So if I do another get pods.

21
00:01:31,590 --> 00:01:32,150
There we go.

22
00:01:32,160 --> 00:01:38,470
There's a brand new pod so because we restart the pod Nats was clearly restarted.

23
00:01:38,500 --> 00:01:41,670
We don't have any of the events that we previously had emitted.

24
00:01:41,710 --> 00:01:45,190
And so if we start to connect with some new service or something like that we're not going to get a

25
00:01:45,190 --> 00:01:50,380
bunch of trash data along that subject or that channel of ticket colon created.

26
00:01:50,450 --> 00:01:55,670
Now of course moving forward in the course at any point time if you are feeling like your Nats deployment

27
00:01:55,700 --> 00:01:59,450
has a ton of trash data inside of it you just will repeat these same steps.

28
00:01:59,450 --> 00:02:05,190
You'll do a delete pod then just verify that a new one was created by data points.

29
00:02:05,450 --> 00:02:09,560
That's good another quick pause work on tickets in just a moment.